- asdf-devel - mailman3.common-lisp.net

trying some ASDF tests on Windows (was: Re: [asdf-devel] Volunteer for LispWorks testing?)
by Dave Cooper 08 Apr '15

08 Apr '15

Hi Robert, [also cc'ing this to asdf-devel in case anyone else has feedback] Ok, shifting gears a little bit here first... I'm trying a few test runs of the ASDF test suite on Windows. Platforms on Windows which I have available to test right now are: Allegro CL (several variations), and CCL. To prepare to run the tests on Windows, I installed cygwin and cygwin's make. Then to run the tests, I do (for lack of having this more automated so far): 1. set ASDF_TEST_LISPS appropriately. 2. Edit run-tests.sh to point to appropriate Lisp executables. 3 Invoke "make test-all-no-upgrade" from the cygwin command shell. Let's try CCL first. Here are the outputs: https://www.dropbox.com/sh/jc2cqwpkp06dupm/-vvd5gFwTk/cl/tests/asdf/output/… Summary: 42 out of 47 pass (5 failures). I can try to dive into these further, but I thought I would post the results here first in case anything is obvious to anyone. Incidentally, I have been running ASDF in production with Allegro CL for some time now (including asdf:monolithic-fasl-op) and it has been working well. There are some startup glitches for running ASDF tests on Windows/Allegro right now. After the CCL issue is resolved I will return to trying to get the tests to run for Allegro on Windows. Regards, Dave P.S. I can see the Launchpad link you sent earlier. On Tue, Sep 3, 2013 at 8:41 PM, Robert P. Goldman <rpgoldman(a)sift.info>wrote: > Dave Cooper wrote: > > In the meantime do you think it's worth me diving into what is > > apparently this one test failure on LWM? > > That would be great, thanks! > > If there is anything I can do to help you get acclimated and figure it > out, let me know. I haven't had a chance to look into it yet. I've > been on vacation and now I'm in the thick of things at work. > > I will try to put some notes in the ASDF ticket on launchpad. Can you > see that? If not, please let me know. > > Best, > Robert > > > > -- My Best, Dave Cooper, Genworks Support david.cooper(a)genworks.com, dave.genworks.com(skype) USA: 248-327-3253(o), 1-248-330-2979(mobile) UK: 0191 645 1699

3 2

[asdf-devel] asdf loading error error
by Cyrus Harmon 08 Apr '15

08 Apr '15

While trying to load and asdf system that generates an error (that’s another story, presumably an abcl-contrib problem), I get the following error: Error while trying to load definition for system abcl-cdk from pathname /Users/sly/projects/abcl-cdk/abcl-cdk.asd: There is no applicable method for the generic function #<STANDARD-GENERIC-FUNCTION ASDF/SYSTEM:BUILTIN-SYSTEM-P {4DE3AFA9}> when called with arguments ((NIL)). [Condition of type ASDF/FIND-SYSTEM:LOAD-SYSTEM-DEFINITION-ERROR] Restarts: 0: [REINITIALIZE-SOURCE-REGISTRY-AND-RETRY] Retry finding system abcl-cdk after reinitializing the source-registry. 1: [RETRY] Retry SLIME REPL evaluation request. 2: [*ABORT] Return to SLIME's top level. 3: [ABORT] Abort thread. Backtrace: 0: (#<FUNCTION {55860583}> #<ASDF/FIND-SYSTEM:LOAD-SYSTEM-DEFINITION-ERROR {7A5599D4}> #<FUNCTION {55860583}>) 1: (APPLY #<FUNCTION {55860583}> (#<ASDF/FIND-SYSTEM:LOAD-SYSTEM-DEFINITION-ERROR {7A5599D4}> #<FUNCTION {55860583}>)) 2: (SYSTEM::RUN-HOOK SYSTEM::*INVOKE-DEBUGGER-HOOK* #<ASDF/FIND-SYSTEM:LOAD-SYSTEM-DEFINITION-ERROR {7A5599D4}> #<FUNCTION {55860583}>) 3: (INVOKE-DEBUGGER #<ASDF/FIND-SYSTEM:LOAD-SYSTEM-DEFINITION-ERROR {7A5599D4}>) 4: (ERROR ASDF/FIND-SYSTEM:LOAD-SYSTEM-DEFINITION-ERROR :NAME "abcl-cdk" :PATHNAME #P"/Users/sly/projects/abcl-cdk/abcl-cdk.asd" ...) 5: (#<FUNCTION {76BF4B40}> #<SIMPLE-ERROR {9E66C0B}>) 6: (SIGNAL #<SIMPLE-ERROR {9E66C0B}>) 7: (ERROR "There is no applicable method for the generic function ~S ~ when called with arguments ~S." #<STANDARD-GENERIC-FUNCTION {4DE3AFA9}> ((NIL))) 8: (#<FUNCTION {372CC276}> #<STANDARD-GENERIC-FUNCTION {4DE3AFA9}> (NIL)) 9: (APPLY #<FUNCTION {372CC276}> (#<STANDARD-GENERIC-FUNCTION {4DE3AFA9}> (NIL))) 10: (ASDF/SYSTEM:BUILTIN-SYSTEM-P NIL) 11: (#<FUNCTION {8E593A8}> "~S: ~S doesn't follow asdf version numbering convention" UIOP/UTILITY:PARSE-VERSION "1.5.6-SNAPSHOT") 12: (APPLY #<FUNCTION {8E593A8}> ("~S: ~S doesn't follow asdf version numbering convention" UIOP/UTILITY:PARSE-VERSION "1.5.6-SNAPSHOT")) 13: (UIOP/UTILITY:CALL-FUNCTION #<FUNCTION {8E593A8}> "~S: ~S doesn't follow asdf version numbering convention" UIOP/UTILITY:PARSE-VERSION "1.5.6-SNAPSHOT") 14: (UIOP/UTILITY:PARSE-VERSION "1.5.6-SNAPSHOT" #<FUNCTION {8E593A8}>) 15: (ASDF/PARSE-DEFSYSTEM::NORMALIZE-VERSION "1.5.6-SNAPSHOT" :COMPONENT "org.openscience.cdk/cdk" :PARENT #<ASDF/SYSTEM:SYSTEM {43A2DC5E}> ...) 16: (ASDF/PARSE-DEFSYSTEM:PARSE-COMPONENT-FORM #<ASDF/SYSTEM:SYSTEM {43A2DC5E}> (:MVN "org.openscience.cdk/cdk" :VERSION "1.5.6-SNAPSHOT") :PREVIOUS-SERIAL-COMPONENT "org.freehep/freehep-graphicsio-svg") 17: (ASDF/PARSE-DEFSYSTEM:PARSE-COMPONENT-FORM NIL (:MODULE "abcl-cdk" :PATHNAME NIL :NAME "abcl-cdk" ...)) I can understand the first error, but the second error that gets generated along the way seems like a mistake. Let me know if I can offer more information to help track this down. thanks, Cyrus

4 6

[asdf-devel] cmucl upgrade of asdf works (somewhat)
by Faré 08 Apr '15

08 Apr '15

An innocuous-looking change suggested by rpgoldman, of not providing a default initform for the selfward-operation slot, led after testing to fixing a few innocuous bugs in asdf, but also to a better understanding of the issues with CMUCL and upgrade. After the innocuous change, tests failed on CMUCL that didn't; some of it was bugs in ASDF that had been papered over by that initform: things that shouldn't have been selfward-operation were, and now had no initform — that was easily fixed. Then, there was a CMUCL bug, whereby sometimes, for reasons not understood yet deterministic and easy but not simple to trigger, some operations would be created without an initialized selfward-operation slot. This was worked around by noticing that selfward-operation was meant to be an :allocation :class slot, but that option wasn't inherited by slot specializations, and needed to be explicitly specified every time the slot was specialized (no doubt because trying to inherit the option would require a non-trivial decision procedure in case of conflict between multiple super-slots); fixing ASDF to do the right thing papered over that CMUCL bug. (to reproduce, checkout 3.1.0.37 and make t l=cmucl t=test-encodings.script) While we were experimenting with CLOS and CMUCL, we tried to remove the #+cmu declaim optimize (not sure why it was ever there), and/or add a #+cmu (setf c::top-level-lambda-max 0). That didn't help (yet I removed the declaim at rtoy's suggestion), but along the way, we noticed that upgrade works from 3.0.1, 3.0.2, 3.0.3, and fails from 2.32 and earlier. The issue is that defclass component has a renamed a slot, and its subclass system is invalidated, but CMUCL somehow fails to finalize it again before it's next used. The good news is that not only have we identified two CMUCL bugs, we have established to upgrade works from 3.0.1 to 3.0.3, which is all that matters, really, since CMUCL updates its ASDF frequently. And we know what to do to avoid more upgrade woes on CMUCL: avoid incompatible slot definitions in classes and/or superclasses. I changed our tests to upgrade versions in reverse chronological order, which is more relevant, and disabled older versions when using CMUCL. I also bumped *oldest-forward-compatible-asdf-version* to 2.33, since we don't have a method on update-instance-for-redefined-class to account for the renamed slot. That leaves the upgrade issue found by cl-grid-test on CCL with cl-l10n and some other systems. wow. such procrastination. much bugfix. very robustified. wow. All because rpgoldman read the source and wanted a tiny cleanup. In other news, still no date set for the walkthrough of ASDF sources on Google hangout; since rpgoldman is the primary audience, we're waiting for his schedule to open up. —♯ƒ • François-René ÐVB Rideau •Reflection&Cybernethics• http://fare.tunes.org "I believe that sex is one of the most beautiful, natural, wholesome things that money can buy." — Steve Martin

3 6

[asdf-devel] BUILD-OP
by Robert P. Goldman 08 Apr '15

08 Apr '15

I'm a little concerned about making BUILD-OP be the default operation. It seems to me that "BUILD" is not a good synonym for "LOAD," which is how BUILD-OP is currently interpreted. I think the conventional interpretation of the word "build" would suggest to the user that (build "foo-system") would compile and NOT load "foo-system," instead of performing LOAD-OP as now. To me "build" does not connote "load." Is this just me? What's the sense of the community? Should we use a different term? I realize that LOAD is taken, and shadowing CL:LOAD would be a big PITA. Is there a synonym we can use? Best, r

5 25

[asdf-devel] Will you please test the latest ASDF with CMUCL
by Robert Goldman 08 Apr '15

08 Apr '15

On Mac OS X for me, it fails upgrade from 2.32 to the latest (3.0.2.2) using method require. Faré's testing instructions are: /usr/local/bin/cmucl -noinit then copy/paste: (load"test/script-support.lisp") (asdf-test::da) (test-upgrade 'load-asdf-lisp'load-asdf-lisp-clean "REQUIRE") I get an error as follows: Error in function KERNEL:CLASS-TYPEP: Class is currently invalid: #<KERNEL::STANDARD-CLASS ASDF/SYSTEM:SYSTEM {48589A35}> Please let me know any findings. I'd like to get this fixed (or disconfirmed) before we release 3.0.3. Best, r

2 2

Re: [asdf-devel] ASDF 3.0.2.1 released
by Faré 08 Apr '15

08 Apr '15

Dear Robert, here are some code review comments on ASDF 3.0.2.1. * Putting :asdf/find-system after :asdf in the recycle looks like it's defeating the purpose; you might as well remove it. * Maybe refactor duplicate-names so it doesn't inherit from system-definition-error ? Or have a function of the same name be called that is defined later to throw the error? * Since we don't work on antique cmucl, maybe we could check whether the :report print-object hack is still needed? * I kind of wanted to prevent the multiplication of .asd files and the eating away of the namespace by using test-asdf/foo systems for new systems; but it's your baby, so your call. Also, an error might not be compatible with putting it in test-asdf.asd. On the other hand, that's a case where define-test-system and/or eval can be used so you don't need a .asd file at all. * the nodes in the grammar could be renamed to be less confusing and not require a comment. —♯ƒ • François-René ÐVB Rideau •Reflection&Cybernethics• http://fare.tunes.org The politicians have a most touching faith in technology — that it can make up for any dumb thing the politicians decide to do. — John McCarthy

3 3

[asdf-devel] Another grammar question
by Robert Goldman 08 Apr '15

08 Apr '15

The :REQUIRE directive seems undocumented. Under what circumstances is it acceptable? thanks, r -- Robert P. Goldman Staff Scientist Smart Information Flow Technologies (d/b/a SIFT, LLC) 211 N. First St., Suite 300 Minneapolis, MN 55401 Voice: (612) 326-3934 Email: rpgoldman(a)SIFT.net

2 5

[asdf-devel] Moderation becoming a problem
by Robert P. Goldman 08 Apr '15

08 Apr '15

I know that "everything in moderation" is a virtue, but "moderating everything" is burdensome. I was glad to see so much interest in the ASDF package, and the corresponding urge to participate in the recent discussion about defining symbols in the keyword package, but if you want to participate in an ongoing discussion, please sign up for the mailing list. Especially with the new, unimproved cl.net mailing list software, moderating a large number of non-member posts is a nuisance. Thanks!

1 0

[asdf-devel] Re: ASDF walkthrough
by Faré 08 Apr '15

08 Apr '15

I put my recording of the ASDF Walkthrough on Youtube. It's nothing great, but oh well, it's as good an introduction to the code as you'll get (for now). It's long, but you can watch at x1.5 speed for reduced bore — or use youtube-dl then vlc to watch at whichever speed you prefer. https://www.youtube.com/watch?v=Qqqbc31ZZ-U The various cleanups suggested during the talk were committed; they were all valid: the testing errors during the session were due to modifying the files while they were being tested. ASDF 3.1.0.60 passes all tests for me. I think Robert has some more comments to add to the code and things to add to the documentation, but I believe that codewise it might already be a release candidate, so please test! —♯ƒ • François-René ÐVB Rideau •Reflection&Cybernethics• http://fare.tunes.org "The Army is a place where you get up early in the morning to be yelled at by people with short haircuts and tiny brains." — Dave Barry

1 0

Re: [asdf-devel] ASDF walkthrough
by Mark Evenson 08 Apr '15

08 Apr '15

Excellent idea! Please let me know when you will be doing this. Currently, I would possibly profit from an explanation of the kinds of "transversal" ASDF does over the "system of systems" it needs to do, but that is not too sharply defined as a question yet. Tersely pecked on my Nexus 5 On Jan 3, 2014 8:10 AM, =?ISO-8859-1?Q?Far=E9?= <fahree(a)gmail.com> wrote: > > Dear Lisp hackers, > > I'm considering recording a walk through the ASDF sources. > > I'd like to have an interactive session over Google Hangout > with one or a few people, explaining the current code in asdf/defsystem > (i.e. not going into uiop, except to minimally explain what asdf uses). > That should take about 2 hours. > > To enjoy the walkthrough, you need to be somewhat fluent in Common Lisp, > and somewhat familiar with how to use ASDF, though not necessarily with > either extending it or hacking its internals. > > If at least one person is familiar with ASDF 2 and has questions, > that could be interesting, or that could be a separate session. > > Please respond me to this email (privately or publicly) if you're interested. > > —♯ƒ • François-René ÐVB Rideau •Reflection&Cybernethics• http://fare.tunes.org > We are always in anarchy. But we pay a hefty price maintaining the illusion > that we aren't, and another one being misled by the illusion. >

1 0