Re: [asdf-devel] testing ASDF with cl-test-grid
Anton == Anton Vodonosov avodono...@yandex.ru writes: Anton 13.03.2013, 04:55, Raymond Toy toy.raym...@gmail.com: Anton == Anton Vodonosov avodono...@yandex.ru writes: Anton 2. test CMUCL 2013-03 snapshot where the bug is fixed. Anton http://common-lisp.net/project/cl-test-grid/asdf/asdf-diff-22-cmucl.html Anton Anton Here we have 3 regressions, all caused by utf8. Either this is another Anton utf8 bug in CMUCL or the source files really contain broken encoding. Unfortunately, another serious error got in to 2013-03. Please try 2013-03-a instead. Anton According to Faré these libraries indeed have latin1 characters. Ah, yes, I see now. I do get utf-8 decoding errors on those three libraries. Thanks for testing this though. Much appreciated. Ray ___ asdf-devel mailing list asdf-devel@common-lisp.net http://lists.common-lisp.net/cgi-bin/mailman/listinfo/asdf-devel
Re: [asdf-devel] testing ASDF with cl-test-grid
Yes, lot of failures in CMUCL 20c + asdf 2.32 tests are caused by an utf8 bug in CMUCL. To rule out this bug and consider only ASDF influence two ways were possible:1. test CMUCL 20c with default encoding http://common-lisp.net/project/cl-test-grid/asdf/asdf-diff-22-cmucl.enc.default.html Strange here is that clim-listener and mcclim-tiff-bitmaps have error and then hang, despite the load operation is run with *debugger-hook* bound to a handler which never hangs. I was unable to reproduce the timeout. We can state that no ASDF related problems are detected by these tests. 2. test CMUCL 2013-03 snapshot where the bug is fixed.http://common-lisp.net/project/cl-test-grid/asdf/asdf-diff-22-cmucl.html Here we have 3 regressions, all caused by utf8. Either this is another utf8 bug in CMUCL or the source files really contain broken encoding. As for testing ACL, I run tests on Express edition (can run it only Windows). Best regards,- Anton ___ asdf-devel mailing list asdf-devel@common-lisp.net http://lists.common-lisp.net/cgi-bin/mailman/listinfo/asdf-devel
Re: [asdf-devel] testing ASDF with cl-test-grid
On Tue, Mar 12, 2013 at 8:18 PM, Anton Vodonosov avodono...@yandex.ru wrote: 2. test CMUCL 2013-03 snapshot where the bug is fixed. http://common-lisp.net/project/cl-test-grid/asdf/asdf-diff-22-cmucl.html Here we have 3 regressions, all caused by utf8. Either this is another utf8 bug in CMUCL or the source files really contain broken encoding. Yes, lispbuilder-regex and cl-bibtex are both known for having latin1 characters. I warned the maintainers a year ago, and they did nothing and didn't reply. We can assume the packages are unhappily unmaintained. There is another fork of regex that was maintained and fixed last year, but this year the maintainer did not respond regarding warnings. —♯ƒ • François-René ÐVB Rideau •ReflectionCybernethics• http://fare.tunes.org Only presidents, editors, and people with tapeworms have the right to use the editorial we. — Mark Twain ___ asdf-devel mailing list asdf-devel@common-lisp.net http://lists.common-lisp.net/cgi-bin/mailman/listinfo/asdf-devel
Re: [asdf-devel] testing ASDF with cl-test-grid
Anton == Anton Vodonosov avodono...@yandex.ru writes: Anton 2. test CMUCL 2013-03 snapshot where the bug is fixed. Anton http://common-lisp.net/project/cl-test-grid/asdf/asdf-diff-22-cmucl.html Anton Anton Here we have 3 regressions, all caused by utf8. Either this is another Anton utf8 bug in CMUCL or the source files really contain broken encoding. Unfortunately, another serious error got in to 2013-03. Please try 2013-03-a instead. or let me know what the 3 regressions are and I can try them myself. Ray ___ asdf-devel mailing list asdf-devel@common-lisp.net http://lists.common-lisp.net/cgi-bin/mailman/listinfo/asdf-devel
Re: [asdf-devel] testing ASDF with cl-test-grid
13.03.2013, 04:55, Raymond Toy toy.raym...@gmail.com: Anton == Anton Vodonosov avodono...@yandex.ru writes: Anton 2. test CMUCL 2013-03 snapshot where the bug is fixed. Anton http://common-lisp.net/project/cl-test-grid/asdf/asdf-diff-22-cmucl.html Anton Anton Here we have 3 regressions, all caused by utf8. Either this is another Anton utf8 bug in CMUCL or the source files really contain broken encoding. Unfortunately, another serious error got in to 2013-03. Please try 2013-03-a instead. According to Faré these libraries indeed have latin1 characters. or let me know what the 3 regressions are and I can try them myself. See the link. In the table, column quicklisp 2013-02-17 + asdf.2.32 contains test results of this qucklisp patched to use ASDF 2.32. (LOAD bibtex FAIL) means that (ql:quickload :bibtex :verbose t) fails. Other two are (LOAD lispbuilder-lexer FAIL) and (LOAD lispbuilder-regex FAIL). - Anton ___ asdf-devel mailing list asdf-devel@common-lisp.net http://lists.common-lisp.net/cgi-bin/mailman/listinfo/asdf-devel
Re: [asdf-devel] testing ASDF with cl-test-grid
http://common-lisp.net/project/cl-test-grid/asdf/asdf-diff-21.html ABCL results also have no new failures. But CMUCL still has problem: http://common-lisp.net/project/cl-test-grid/asdf/asdf-diff-21-cmucl.html Here we compare with quicklisp 2012-02-17 patched so that it doesn't (require 'asdf) before loading it's own ASDF, and so overcoming the ASDF upgrade issue present in the current quicklisp. I.e. the same codebase is tested 1) with ASDF 2.26 without upgrade 2) with to ASDF 2.31.8 loaded after the (require 'asdf). Most of the failures are due to the same error: -330 is not of type (OR (MOD 536870911) NULL) I am not sure what it is, probably some kind of utf-8 related bug. ___ asdf-devel mailing list asdf-devel@common-lisp.net http://lists.common-lisp.net/cgi-bin/mailman/listinfo/asdf-devel
Re: [asdf-devel] testing ASDF with cl-test-grid
But CMUCL still has problem: http://common-lisp.net/project/cl-test-grid/asdf/asdf-diff-21-cmucl.html Most of the failures are due to the same error: -330 is not of type (OR (MOD 536870911) NULL) I am not sure what it is, probably some kind of utf-8 related bug. We've had that failure in the past, on an old version of CMUCL, then it disappeared with a more recent one. Which version are you using? —♯ƒ • François-René ÐVB Rideau •ReflectionCybernethics• http://fare.tunes.org What one person receives without working for, another person must work for without receiving. — Adrian Rogers ___ asdf-devel mailing list asdf-devel@common-lisp.net http://lists.common-lisp.net/cgi-bin/mailman/listinfo/asdf-devel
Re: [asdf-devel] testing ASDF with cl-test-grid
Is anyone running the tests on ACL any more? thanks, r ___ asdf-devel mailing list asdf-devel@common-lisp.net http://lists.common-lisp.net/cgi-bin/mailman/listinfo/asdf-devel
Re: [asdf-devel] testing ASDF with cl-test-grid
Anton == Anton Vodonosov avodono...@yandex.ru writes: Anton http://common-lisp.net/project/cl-test-grid/asdf/asdf-diff-21.html Anton ABCL results also have no new failures. Anton But CMUCL still has problem: Anton http://common-lisp.net/project/cl-test-grid/asdf/asdf-diff-21-cmucl.html Anton Here we compare with quicklisp 2012-02-17 patched so that it doesn't Anton (require 'asdf) before loading it's own ASDF, and so overcoming Anton the ASDF upgrade issue present in the current quicklisp. Anton I.e. the same codebase is tested 1) with ASDF 2.26 without upgrade Anton 2) with to ASDF 2.31.8 loaded after the (require 'asdf). Anton Most of the failures are due to the same error: Anton -330 is not of type (OR (MOD 536870911) NULL) Anton I am not sure what it is, probably some kind of utf-8 related bug. I only checked a few of the failed tests so far. They do look like some shortcomings in unicode support but others do not. I also see that it looks like you're using cmucl 20c. That's pretty old. The utf-8 bug that you reported recently has been fixed and is now available in the 2013-03 snapshot from trac.common-lisp.net/cmucl. Ray ___ asdf-devel mailing list asdf-devel@common-lisp.net http://lists.common-lisp.net/cgi-bin/mailman/listinfo/asdf-devel
Re: [asdf-devel] testing ASDF with cl-test-grid
I'm intending to do routine cl-test-grid testing with ACL (Linux and WIndows) but I still have to get a proper automated testbed set up. I have been working with the latest ASDF but have not been doing rigorous cl-test-grid testing with it yet. On Tue, Mar 5, 2013 at 11:53 AM, Robert Goldman rpgold...@sift.info wrote: Is anyone running the tests on ACL any more? thanks, r ___ asdf-devel mailing list asdf-devel@common-lisp.net http://lists.common-lisp.net/cgi-bin/mailman/listinfo/asdf-devel -- My Best, Dave Cooper, Genworks Support david.coo...@genworks.com, dave.genworks.com(skype) USA: 248-327-3253(o), 1-248-330-2979(mobile) UK: 0191 645 1699 ___ asdf-devel mailing list asdf-devel@common-lisp.net http://lists.common-lisp.net/cgi-bin/mailman/listinfo/asdf-devel
Re: [asdf-devel] testing ASDF with cl-test-grid
http://common-lisp.net/project/cl-test-grid/asdf/asdf-diff-21.html CLISP and ECL results are ready - nothing new. CMUCL results are also ready, but we can't compare them with nonpatched quicklisp, as current quicklisp doesn't support CMUCL out of box. I have compared them with the last quicklisp supported CMUCL, but due to cl-fad issue in the last quicklisp (https://github.com/edicl/cl-fad/issues/6) the table contains many unrelated failures: http://common-lisp.net/project/cl-test-grid/asdf/asdf-diff-21-cmucl.html To have a better comparison base I think to run CMUCL tests on quicklisp 2012-02-17 fixed so that it works with its own ASDF. Will do so after ABCL tests are finished. ___ asdf-devel mailing list asdf-devel@common-lisp.net http://lists.common-lisp.net/cgi-bin/mailman/listinfo/asdf-devel
Re: [asdf-devel] testing ASDF with cl-test-grid
As there were some fixes, running tests again. ASDF version 2.31.8Quicklisp version is shifted to 2013-02-17. SBCL results arrived already:http://common-lisp.net/project/cl-test-grid/asdf/asdf-diff-21.html Other will follow. ___ asdf-devel mailing list asdf-devel@common-lisp.net http://lists.common-lisp.net/cgi-bin/mailman/listinfo/asdf-devel
Re: [asdf-devel] testing ASDF with cl-test-grid
04.03.2013, 05:49, Faré f...@tunes.org: OK, so the results are massively positive, and the failures all known and most of them already fixed upstream. I'll ping keithj again — he fixed cl-sam already, but still hasn't fixed deoxybytes-systems. Apart from that, the only system that looks like it loses and doesn't have a fix yet is buildapp, but I'm confident Xach will fix it sooner than later. Positive changes are mostly due to utf-8. Yes, buildapp is the only new regression we haven't seen before. Meantime, the table is updated with CCL results: http://common-lisp.net/project/cl-test-grid/asdf/asdf-diff-21.html Nothing new on CCL, we saw all these failures previously. ___ asdf-devel mailing list asdf-devel@common-lisp.net http://lists.common-lisp.net/cgi-bin/mailman/listinfo/asdf-devel
Re: [asdf-devel] testing ASDF with cl-test-grid
On Sun, Mar 3, 2013 at 9:39 PM, Anton Vodonosov avodono...@yandex.ru wrote: 04.03.2013, 05:49, Faré f...@tunes.org: OK, so the results are massively positive, and the failures all known and most of them already fixed upstream. I'll ping keithj again — he fixed cl-sam already, but still hasn't fixed deoxybytes-systems. Apart from that, the only system that looks like it loses and doesn't have a fix yet is buildapp, but I'm confident Xach will fix it sooner than later. Positive changes are mostly due to utf-8. Yes, buildapp is the only new regression we haven't seen before. Oh, we have seen it before. It's just that Xach is still in wait and see mode regarding ASDF, and not moving on that one, yet. Meantime, the table is updated with CCL results: http://common-lisp.net/project/cl-test-grid/asdf/asdf-diff-21.html Nothing new on CCL, we saw all these failures previously. OK. I'll run some tests from work tomorrow, and release an ASDF 2.32. —♯ƒ • François-René ÐVB Rideau •ReflectionCybernethics• http://fare.tunes.org First they ignore you. Then they laugh at you. Then they fight you. Then you win. — Gandhi ___ asdf-devel mailing list asdf-devel@common-lisp.net http://lists.common-lisp.net/cgi-bin/mailman/listinfo/asdf-devel
Re: [asdf-devel] testing ASDF with cl-test-grid
Performed tests with ABCL and ACL (express edition, and on Windows, as my linux system turns out to be too old to run ACL 9.0 and the ACL 8.0 Express license has expired). http://common-lisp.net/project/cl-test-grid/asdf/asdf-diff-20.html ACL shows new problem with portableaserve and via it with all genworks-gdl systems. The error: No defined method for ASDF/ACTION:PERFORM oncompiling #ORIGINAL-ASERVE aserve dummy Aside from that all the failures are (upstream) library errors we saw already on other lisps. All the CRASH results are to be ignored. They are caused by heap size limitation of the ACL Express edition. ABCL shows no new problems. All the failures are upstream library errors we saw already on other lisps and com.informatimago.common-lisp TIMEOUT due to http://trac.common-lisp.net/armedbear/ticket/274. Best regards, - Anton ___ asdf-devel mailing list asdf-devel@common-lisp.net http://lists.common-lisp.net/cgi-bin/mailman/listinfo/asdf-devel
Re: [asdf-devel] testing ASDF with cl-test-grid
On Thu, Feb 28, 2013 at 8:46 PM, Dave Cooper david.coo...@genworks.comwrote: ACL shows new problem with portableaserve and via it with all genworks-gdl systems. The error: No defined method for ASDF/ACTION:PERFORM oncompiling #ORIGINAL-ASERVE aserve dummy By the way, what is this oncompiling operation you speak of? I'm not seeing a literal oncompiling anywhere in ASDF 2.31.4 ... This is a hack in aserve.asd to allow (asdf:load-system :aserve) to bring in the original aserve (via require) in the case of #+allegro. There are some defclass'es and defmethod'd in the middle of the .asd file to enable this. Maybe this doesn't work so well with ASDF3? Or maybe they just need some (eval-when (...) ...) around them (at the risk of mental health issues)? Here is what the stuff looks like: #+allegro (defclass original-aserve (asdf:component) ((loaded :initform nil :accessor loaded))) #+allegro (defmethod asdf:source-file-type ((c original-aserve) (s module)) dummy) #+allegro (defmethod asdf:perform ((op asdf:load-op) (c original-aserve)) #+common-lisp-controller (c-l-c:original-require 'aserve) #-common-lisp-controller (require 'aserve) (setf (loaded c) t)) #+allegro (defmethod asdf:operation-done-p ((op asdf:load-op) (c original-aserve)) (loaded c)) #+allegro (defmethod asdf:operation-done-p ((op asdf:compile-op) (c original-aserve)) t) #+allegro (defsystem aserve :components ((:original-aserve dummy))) -- My Best, Dave Cooper, Genworks Support david.coo...@genworks.com, dave.genworks.com(skype) USA: 248-327-3253(o), 1-248-330-2979(mobile) UK: 0191 645 1699 -- My Best, Dave Cooper, Genworks Support david.coo...@genworks.com, dave.genworks.com(skype) USA: 248-327-3253(o), 1-248-330-2979(mobile) UK: 0191 645 1699 ___ asdf-devel mailing list asdf-devel@common-lisp.net http://lists.common-lisp.net/cgi-bin/mailman/listinfo/asdf-devel
Re: [asdf-devel] testing ASDF with cl-test-grid
01.03.2013, 05:57, Dave Cooper david.coo...@genworks.com: On Thu, Feb 28, 2013 at 8:46 PM, Dave Cooper david.coo...@genworks.com wrote: ACL shows new problem with portableaserve and via it with all genworks-gdl systems. The error: No defined method for ASDF/ACTION:PERFORM oncompiling #ORIGINAL-ASERVE aserve dummy By the way, what is this oncompiling operation you speak of? I'm not seeing a literal oncompiling anywhere in ASDF 2.31.4 ... Sorry, it is a copy/paste error. Actually it is on compiling ___ asdf-devel mailing list asdf-devel@common-lisp.net http://lists.common-lisp.net/cgi-bin/mailman/listinfo/asdf-devel
Re: [asdf-devel] testing ASDF with cl-test-grid
By the way how can I replicate this myself for testing? For testing of specific systems, just temporarily replace the asdf in my implementation with ASDF 2.31.4, then proceed with quicklisp as usual? For trying cl-test-grid with a cutting edge ASDF what is the recommended approach? On Thu, Feb 28, 2013 at 8:46 PM, Dave Cooper david.coo...@genworks.comwrote: ACL shows new problem with portableaserve and via it with all genworks-gdl systems. The error: No defined method for ASDF/ACTION:PERFORM oncompiling #ORIGINAL-ASERVE aserve dummy This is a hack in aserve.asd to allow (asdf:load-system :aserve) to bring in the original aserve (via require) in the case of #+allegro. There are some defclass'es and defmethod'd in the middle of the .asd file to enable this. Maybe this doesn't work so well with ASDF3? Or maybe they just need some (eval-when (...) ...) around them (at the risk of mental health issues)? Here is what the stuff looks like: #+allegro (defclass original-aserve (asdf:component) ((loaded :initform nil :accessor loaded))) #+allegro (defmethod asdf:source-file-type ((c original-aserve) (s module)) dummy) #+allegro (defmethod asdf:perform ((op asdf:load-op) (c original-aserve)) #+common-lisp-controller (c-l-c:original-require 'aserve) #-common-lisp-controller (require 'aserve) (setf (loaded c) t)) #+allegro (defmethod asdf:operation-done-p ((op asdf:load-op) (c original-aserve)) (loaded c)) #+allegro (defmethod asdf:operation-done-p ((op asdf:compile-op) (c original-aserve)) t) #+allegro (defsystem aserve :components ((:original-aserve dummy))) -- My Best, Dave Cooper, Genworks Support david.coo...@genworks.com, dave.genworks.com(skype) USA: 248-327-3253(o), 1-248-330-2979(mobile) UK: 0191 645 1699 -- My Best, Dave Cooper, Genworks Support david.coo...@genworks.com, dave.genworks.com(skype) USA: 248-327-3253(o), 1-248-330-2979(mobile) UK: 0191 645 1699 ___ asdf-devel mailing list asdf-devel@common-lisp.net http://lists.common-lisp.net/cgi-bin/mailman/listinfo/asdf-devel
Re: [asdf-devel] testing ASDF with cl-test-grid
01.03.2013, 07:37, Anton Vodonosov avodono...@yandex.ru: I patch quicklisp. I have a directory quicklisp-patched for this purpose. Copy new asdf.lisp to quicklisp-patched/asdf.lisp and edit quicklisp-patched/setup.lisp to change (defvar *required-asdf-version* 2.26) to (defvar *required-asdf-version* 2.31.4) If it's also necessary to include patched versions of some libraries into testing, they are places/symlinked to quicklisp-patched/local-projects ___ asdf-devel mailing list asdf-devel@common-lisp.net http://lists.common-lisp.net/cgi-bin/mailman/listinfo/asdf-devel
Re: [asdf-devel] testing ASDF with cl-test-grid
On Thu, Feb 28, 2013 at 8:29 PM, Anton Vodonosov avodono...@yandex.ruwrote: http://common-lisp.net/project/cl-test-grid/asdf/asdf-diff-20.html ACL shows new problem with portableaserve and via it with all genworks-gdl systems. The error: No defined method for ASDF/ACTION:PERFORM oncompiling #ORIGINAL-ASERVE aserve dummy This is fixed by adding an empty method as follows to aserve.asd: ;;; #+allegro (defmethod asdf:perform ((op asdf:compile-op) (c original-aserve))) ;;; I will get a patch to Rudi Schlatte for updating of the portableaserve on sourceforge (this is the one used by Quicklisp). -- My Best, Dave Cooper, Genworks Support david.coo...@genworks.com, dave.genworks.com(skype) USA: 248-327-3253(o), 1-248-330-2979(mobile) UK: 0191 645 1699 ___ asdf-devel mailing list asdf-devel@common-lisp.net http://lists.common-lisp.net/cgi-bin/mailman/listinfo/asdf-devel
Re: [asdf-devel] testing ASDF with cl-test-grid
23.02.2013, 08:48, Anton Vodonosov avodono...@yandex.ru: ECL results for ASFD 2.30.5: http://common-lisp.net/project/cl-test-grid/asdf/asdf-diff-17.html I have reivewded the ECL results. The (upstream) errors we have seen already on other CL implementations: - cl-prolog - deoxybyte-utilities - meta-sexp - qbook - xcvb-bridge Other not regressions: - opticl-doc - Not a regression. This ASDF system generates a documentation .html file from .md file. The output .html file is placed near the source file. This operation failes on ECL, but when .html is alreay present the operation is skipped. Interestengly, that new ASDF also rebuilds the ASDF system when dependencies are recompiled, so the failure is visible more often - jwacs - too heavy compilation for gcc (long, and finally gcc runs out of heap) - jwacs-tests - too heavy compilation for gcc (long, and finally gcc runs out of heap) - hu.dwim.serializer - (caused by https://github.com/quicklisp/quicklisp-client/issues/71) - hu.dwim.serializer.test - (caused by https://github.com/quicklisp/quicklisp-client/issues/71) Thigs deserving attention: - blas-complex - blas-real These two seem to be a problem of ASDF integration with cl:require. To reproduce: ./lisps/ecl-bin-12.12.1/bin/ecl -norc -eval '(ext::install-bytecodes-compiler)' -load quicklisp-patched2/setup.lisp -eval '(ql:quickload :blas-complex)' Compare to the following, with succeeds: ./lisps/ecl-bin-12.12.1/bin/ecl -norc -eval '(ext::install-bytecodes-compiler)' -load quicklisp/setup.lisp -eval '(ql:quickload :blas-complex)' - a2x-test - Fare, you might want to review. The error is strange - Found invalid character Rubout. To reproduce: ./lisps/ecl-bin-12.12.1/bin/ecl -norc -eval '(ext::install-bytecodes-compiler)' -load quicklisp-patched2/setup.lisp -eval '(ql:quickload :a2x-test)' In constrast to old ASDF: ./lisps/ecl-bin-12.12.1/bin/ecl -norc -eval '(ext::install-bytecodes-compiler)' -load quicklisp/setup.lisp -eval '(ql:quickload :a2x-test)' ___ asdf-devel mailing list asdf-devel@common-lisp.net http://lists.common-lisp.net/cgi-bin/mailman/listinfo/asdf-devel
Re: [asdf-devel] testing ASDF with cl-test-grid
Thigs deserving attention: - blas-complex - blas-real These two seem to be a problem of ASDF integration with cl:require. To reproduce: ./lisps/ecl-bin-12.12.1/bin/ecl -norc -eval '(ext::install-bytecodes-compiler)' -load quicklisp-patched2/setup.lisp -eval '(ql:quickload :blas-complex)' Compare to the following, with succeeds: ./lisps/ecl-bin-12.12.1/bin/ecl -norc -eval '(ext::install-bytecodes-compiler)' -load quicklisp/setup.lisp -eval '(ql:quickload :blas-complex)' Aha. A bug in ASDF. Fixed in 2.30.9. I will include a regression test in next commit. It's also a bug in blas-complex to use (require 'f2cl) when it should be using asdf dependencies instead. - a2x-test - Fare, you might want to review. Don't worry about a2x-test. It's part of xcvb, and xcvb isn't going to get much love until all current ASDF issues are resolved. —♯ƒ • François-René ÐVB Rideau •ReflectionCybernethics• http://fare.tunes.org It has been my observation that most people get ahead during the time that others waste. — Henry Ford ___ asdf-devel mailing list asdf-devel@common-lisp.net http://lists.common-lisp.net/cgi-bin/mailman/listinfo/asdf-devel
Re: [asdf-devel] testing ASDF with cl-test-grid
22.02.2013, 22:38, Anton Vodonosov avodono...@yandex.ru: Results for ECL, lisp-to-c compiler: http://common-lisp.net/project/cl-test-grid/asdf/asdf-diff-16.html Most of the systems fails with the same error: Unhandled SERIOUS-CONDITION of type SIMPLE-ERROR is signaled: No defined method for ASDF/ACTION:PERFORM on compiling #compiled-file sockets sockets The problem nails down to usocket.asd depending on :sb-bsd-sockets. It ma be reroduced lik this: lisps/ecl-bin-12.12.1/bin/ecl -norc -load asdf/build/asdf.lisp (asdf:operate 'asdf:load-op :sb-bsd-sockets) Condition of type: SIMPLE-ERROR No defined method for ASDF/ACTION:PERFORM on compiling #compiled-file sockets sockets Available restarts: 1. (RETRY) Retry compiling #compiled-file sockets sockets. 2. (ACCEPT) Continue, treating compiling #compiled-file sockets sockets as having been successful. 3. (RESTART-TOPLEVEL) Go back to Top-Level REPL. Broken at LAMBDA. In: #process TOP-LEVEL. File: #P/home/testgrid/asdf/build/asdf.lisp (Position #306038) ___ asdf-devel mailing list asdf-devel@common-lisp.net http://lists.common-lisp.net/cgi-bin/mailman/listinfo/asdf-devel
Re: [asdf-devel] testing ASDF with cl-test-grid
That smells like a bug in ECL. This works: rlwrap ecl -norc -eval \ '(#.(require :asdf) #.(format t \~S~%\ (asdf:asdf-version)) #.(asdf:load-system :sockets)) 2.26.6 This doesn't: rlwrap ecl -norc -load asdf/build/asdf.lisp -eval '(#.(require :asdf) #.(format t \~S~%\ (asdf:asdf-version)) #.(asdf:load-system :sockets)) 2.30.3 No defined method for ASDF/ACTION:PERFORM on compiling #compiled-file sockets sockets. If I just query from rlwrap /home/testgrid/lisps/ecl-bin-12.12.1/bin/ecl -norc -load asdf/build/asdf.lisp I get: (COMPUTE-APPLICABLE-METHODS #'asdf:perform (list (make-instance 'asdf:compile-op :force t) (asdf:find-component :sockets sockets))) (#standard-method PERFORM (#The STANDARD-CLASS ASDF/OPERATION:OPERATION #The STANDARD-CLASS ASDF/COMPONENT:COMPONENT) #standard-method PERFORM (#The STANDARD-CLASS ASDF/OPERATION:OPERATION #The STANDARD-CLASS ASDF/COMPONENT:COMPONENT) #standard-method PERFORM (#The STANDARD-CLASS ASDF/OPERATION:OPERATION #The BUILT-IN-CLASS T) #standard-method PERFORM (#The BUILT-IN-CLASS T #The STANDARD-CLASS ASDF/BUNDLE:COMPILED-FILE)) (describe (car (last (COMPUTE-APPLICABLE-METHODS #'asdf:perform (list (make-instance 'asdf:compile-op :force t) (asdf:find-component :sockets sockets)) #standard-method PERFORM (#The BUILT-IN-CLASS T #The STANDARD-CLASS ASDF/BUNDLE:COMPILED-FILE) is an instance of class STANDARD-METHOD it has the following instance slots THE-GENERIC-FUNCTION: #standard-generic-function ASDF/ACTION:PERFORM LAMBDA-LIST:(O C) SPECIALIZERS: (#The BUILT-IN-CLASS T #The STANDARD-CLASS ASDF/BUNDLE:COMPILED-FILE) QUALIFIERS: NIL THE-FUNCTION: #compiled-closure 09de3510 DOCSTRING: NIL PLIST: NIL KEYWORDS: NIL (asdf:perform (make-instance 'asdf:compile-op :force t) (asdf:find-component :sockets sockets)) Condition of type: SIMPLE-ERROR No defined method for ASDF/ACTION:PERFORM on compiling #compiled-file sockets sockets The method that ought to match is this: (defmethod perform (o (c compiled-file)) (declare (ignorable o c)) nil)) Interestingly, that part of the code hasn't changed since ASDF 2.26.6, which works as seen above. However, if I change it to: (defmethod perform ((o operation) (c compiled-file)) (declare (ignorable o c)) nil)) then it works again! And so that is my workaround for 2.30.5. I don't know what causes ECL to not match that method. Is it the new EVAL-WHEN around it? In any case, I believe it's a bug in ECL. —♯ƒ • François-René ÐVB Rideau •ReflectionCybernethics• http://fare.tunes.org If six billion people have both more food and more forest than their three billion parents did; if the prices of copper, wheat and natural gas are going down, not up; if there are 20 times more carcinogens in three cups of organic coffee than in daily dietary exposure to the worst pesticide both before and after the DDT ban; if renewable resources such as whales are more easily exhausted than non-renewables such as coal; if lower infant mortality leads to falling populations, not rising ones, then perhaps we need to think differently about what sustainability means. Perhaps the most sustainable thing we can do is develop new technology, increase trade and spread affluence. — Matt Ridley On Fri, Feb 22, 2013 at 2:07 PM, Anton Vodonosov avodono...@yandex.ru wrote: 22.02.2013, 22:38, Anton Vodonosov avodono...@yandex.ru: Results for ECL, lisp-to-c compiler: http://common-lisp.net/project/cl-test-grid/asdf/asdf-diff-16.html Most of the systems fails with the same error: Unhandled SERIOUS-CONDITION of type SIMPLE-ERROR is signaled: No defined method for ASDF/ACTION:PERFORM on compiling #compiled-file sockets sockets The problem nails down to usocket.asd depending on :sb-bsd-sockets. It ma be reroduced lik this: lisps/ecl-bin-12.12.1/bin/ecl -norc -load asdf/build/asdf.lisp (asdf:operate 'asdf:load-op :sb-bsd-sockets) Condition of type: SIMPLE-ERROR No defined method for ASDF/ACTION:PERFORM on compiling #compiled-file sockets sockets Available restarts: 1. (RETRY) Retry compiling #compiled-file sockets sockets. 2. (ACCEPT) Continue, treating compiling #compiled-file sockets sockets as having been successful. 3. (RESTART-TOPLEVEL) Go back to Top-Level REPL. Broken at LAMBDA. In: #process TOP-LEVEL. File: #P/home/testgrid/asdf/build/asdf.lisp (Position #306038) ___ asdf-devel mailing list asdf-devel@common-lisp.net http://lists.common-lisp.net/cgi-bin/mailman/listinfo/asdf-devel
Re: [asdf-devel] testing ASDF with cl-test-grid
23.02.2013, 02:30, Faré fah...@gmail.com: And so that is my workaround for 2.30.5. I will run the tests ___ asdf-devel mailing list asdf-devel@common-lisp.net http://lists.common-lisp.net/cgi-bin/mailman/listinfo/asdf-devel
Re: [asdf-devel] testing ASDF with cl-test-grid
Pushed. —♯ƒ • François-René ÐVB Rideau •ReflectionCybernethics• http://fare.tunes.org There is no meaning without words, no shape without matter, no soul without body. On Fri, Feb 22, 2013 at 5:35 PM, Anton Vodonosov avodono...@yandex.ru wrote: 23.02.2013, 02:33, Anton Vodonosov avodono...@yandex.ru: 23.02.2013, 02:30, Faré fah...@gmail.com: And so that is my workaround for 2.30.5. I will run the tests when you push it ___ asdf-devel mailing list asdf-devel@common-lisp.net http://lists.common-lisp.net/cgi-bin/mailman/listinfo/asdf-devel
Re: [asdf-devel] testing ASDF with cl-test-grid
ECL results for ASFD 2.30.5: http://common-lisp.net/project/cl-test-grid/asdf/asdf-diff-17.html ___ asdf-devel mailing list asdf-devel@common-lisp.net http://lists.common-lisp.net/cgi-bin/mailman/listinfo/asdf-devel
Re: [asdf-devel] testing ASDF with cl-test-grid
Comparision for building with (setf asdf:*default-encoding* :utf-8): http://common-lisp.net/project/cl-test-grid/asdf/asdf-diff-14.html ___ asdf-devel mailing list asdf-devel@common-lisp.net http://lists.common-lisp.net/cgi-bin/mailman/listinfo/asdf-devel
Re: [asdf-devel] testing ASDF with cl-test-grid
On Thu, Feb 21, 2013 at 6:44 AM, Anton Vodonosov avodono...@yandex.ru wrote: Comparision for building with (setf asdf:*default-encoding* :utf-8): http://common-lisp.net/project/cl-test-grid/asdf/asdf-diff-14.html Wow, it's all positive! Not that surprising, when you think about it. Maybe I should just do it, and change the default. I've been warning people for a year already. —♯ƒ • François-René ÐVB Rideau •ReflectionCybernethics• http://fare.tunes.org Future scholars will only have copies of copies of copies of manuscripts. How will they authenticate what really WAS said in our dark ages? ___ asdf-devel mailing list asdf-devel@common-lisp.net http://lists.common-lisp.net/cgi-bin/mailman/listinfo/asdf-devel
Re: [asdf-devel] testing ASDF with cl-test-grid
On Thu, 2013-02-21 at 08:00 -0500, Faré wrote: On Thu, Feb 21, 2013 at 6:44 AM, Anton Vodonosov avodono...@yandex.ru wrote: Comparision for building with (setf asdf:*default-encoding* :utf-8): http://common-lisp.net/project/cl-test-grid/asdf/asdf-diff-14.html Wow, it's all positive! Not that surprising, when you think about it. Maybe I should just do it, and change the default. I've been warning people for a year already. Go ahead, please. -- Stelian Ionescu a.k.a. fe[nl]ix Quidquid latine dictum sit, altum videtur. http://common-lisp.net/project/iolib signature.asc Description: This is a digitally signed message part ___ asdf-devel mailing list asdf-devel@common-lisp.net http://lists.common-lisp.net/cgi-bin/mailman/listinfo/asdf-devel
Re: [asdf-devel] testing ASDF with cl-test-grid
21.02.2013, 17:27, Stelian Ionescu sione...@cddr.org: On Thu, 2013-02-21 at 08:00 -0500, Faré wrote: On Thu, Feb 21, 2013 at 6:44 AM, Anton Vodonosov avodono...@yandex.ru wrote: Comparision for building with (setf asdf:*default-encoding* :utf-8): http://common-lisp.net/project/cl-test-grid/asdf/asdf-diff-14.html Wow, it's all positive! Not that surprising, when you think about it. Maybe I should just do it, and change the default. I've been warning people for a year already. Go ahead, please. I also support making :utf-8 the default. It will only improve stability, without any harm. Even if someone wants to use some incomatible encoding (but I doubt such people exist, let's say probability of their existence is 0.01), they can always specify :defsystem-depends-on :asdf-encodings :encoding :koi8-r That's 0.5 hour per ASDF system. 0.01 * 0.5 is nothing comparig to how many existing systems will build reliably. In the current situation when source file encoding is environment dependent, the defeloper is often is just unaware that hist ASDF system will not build on other computer. ___ asdf-devel mailing list asdf-devel@common-lisp.net http://lists.common-lisp.net/cgi-bin/mailman/listinfo/asdf-devel
Re: [asdf-devel] testing ASDF with cl-test-grid
OK, I've been convinced by that 100% positive cl-test-grid improvement, and starting with ASDF 2.30.1, :utf-8 is the default value of *default-encoding* (and 2.30.2 enforces the new default when upgrading while preserving non-:default overrides). Now to resurrect, update and process https://github.com/orivej/asdf-encodings/wiki/Tracking-non-UTF-8-lisp-files-in-Quicklisp Grepping through quicklisp finds offending files in the following directories, whether or not they block a clean build: antik-20120909-git binary-types-20101006-git bknr-web-20130128-git cells-20120909-git cl-bibtex-20120909-cvs cl-pdf-20120909-svn cl-png-0.6 cl-typesetting-20120407-svn clfswm-20130128-git clsql-20130128-git def-symbol-readmacro-20130128-hg genworks-gdl-20130128-git lispbuilder-20120909-svn mcclim-20120909-cvs metatilities-20101006-darcs montezuma-20121013-git phemlock-20120909-cvs plain-odbc-20120909-svn utils-kt-20101006-git —♯ƒ • François-René ÐVB Rideau •ReflectionCybernethics• http://fare.tunes.org Taxonomy is the death of science — A. N. Whitehead On Thu, Feb 21, 2013 at 8:40 AM, Anton Vodonosov avodono...@yandex.ru wrote: 21.02.2013, 17:27, Stelian Ionescu sione...@cddr.org: On Thu, 2013-02-21 at 08:00 -0500, Faré wrote: On Thu, Feb 21, 2013 at 6:44 AM, Anton Vodonosov avodono...@yandex.ru wrote: Comparision for building with (setf asdf:*default-encoding* :utf-8): http://common-lisp.net/project/cl-test-grid/asdf/asdf-diff-14.html Wow, it's all positive! Not that surprising, when you think about it. Maybe I should just do it, and change the default. I've been warning people for a year already. Go ahead, please. I also support making :utf-8 the default. It will only improve stability, without any harm. Even if someone wants to use some incomatible encoding (but I doubt such people exist, let's say probability of their existence is 0.01), they can always specify :defsystem-depends-on :asdf-encodings :encoding :koi8-r That's 0.5 hour per ASDF system. 0.01 * 0.5 is nothing comparig to how many existing systems will build reliably. In the current situation when source file encoding is environment dependent, the defeloper is often is just unaware that hist ASDF system will not build on other computer. ___ asdf-devel mailing list asdf-devel@common-lisp.net http://lists.common-lisp.net/cgi-bin/mailman/listinfo/asdf-devel ___ asdf-devel mailing list asdf-devel@common-lisp.net http://lists.common-lisp.net/cgi-bin/mailman/listinfo/asdf-devel
Re: [asdf-devel] testing ASDF with cl-test-grid
21.02.2013, 20:55, Faré fah...@gmail.com: OK, so I contacted each and every maintainer for the systems with warnings, and already got a few of them fixed. Now to test the systems enabled by UTF-8, and see if any have warnings. Anton, can you make a run with ASDF 2.26 + utf-8, then a run with ASDF 2.29 + utf-8 + warnings, so we can see the difference? 2.26 vs 2.29? You mean 2.29 in both cases I believe. We already have asdf.2.29.5-utf8-no-warn, so we only need to perform asdf.2.29.5-utf8. Will start do now. ___ asdf-devel mailing list asdf-devel@common-lisp.net http://lists.common-lisp.net/cgi-bin/mailman/listinfo/asdf-devel
Re: [asdf-devel] testing ASDF with cl-test-grid
20.02.2013, 20:28, Anton Vodonosov avodono...@yandex.ru: That of 1083 ASDF system I was able to ql:quickoad on my linux system with SBCL 1.1.1 and quicklisp 2013-01-28, I can ql:quickoad all of them except for the described above upstream errors on quicklisp 2013-01-28 + ASDF 2.29.5 with patched asdf-system-connections and (setf asdf:*warnings-file-type* nil) - this disables new ASDF3 deferred warnings processing. To clarify, the said asdf-system-connections fix is applied to the library git repo at Feb 10, 2013, thus it must be already in quicklisp. ___ asdf-devel mailing list asdf-devel@common-lisp.net http://lists.common-lisp.net/cgi-bin/mailman/listinfo/asdf-devel
