cl-test-grid results for svn revision 14755
Anton Vodonosov
avodonosov at yandex.ru
Fri Apr 10 23:24:01 UTC 2015
09.04.2015, 23:50, "Erik Huelsmann" <ehuels at gmail.com>:
> http://abcl.org/trac/changeset/14756 fixes the cl-cont problems. After providing enough PermGen memory, I got the other failures to complete correctly (including stmx, btw) now too.
>
> Could you run the tests again to see if *now* there are new successes? (I'm still expecting new successes, but I can't remember which systems were failing that were reporting eliminated dead code in LABELS.)
>
> Regards,
>
> Erik.
Hello,
Here is the report:
https://common-lisp.net/project/cl-test-grid/abcl/abcl-diff26.html
(BTW, the it was run on new quicklisp 2015-04-07)
The only remaining regression is stmx - I suppose caused by
http://abcl.org/trac/ticket/388 as Massimiliano reports. Erik, this error
happens even with large PermGen space - it happens during tests, not during
ql:quickload. You may reproduce with (asdf:test-op :stmx).
The situation with iolib-tests is an improvement. Previous ABCL 1.3.1
catches raw java error:
#<THREAD "interpreter" {1F10B9C}>: Debugger invoked on condition of type ERROR
Caught java.nio.charset.UnsupportedCharsetException: LATIN-1.
Restarts:
0: TOP-LEVEL Return to top level.
while new ABCL wraps the java error into a lisp condition:
Error loading /home/testgrid/.cache/common-lisp/abcl-1.4.0-dev-svn-14756-fasl42-linux-x86/home/testgrid/quicklisp/dists/quicklisp/software/iolib-20150302-git/tests/sockets.abcl at line 9 (offset 542)
#<THREAD "interpreter" {C5B62D}>: Debugger invoked on condition of type SIMPLE-ERROR
Undefined encoding: LATIN-1
Restarts:
0: TRY-RECOMPILING Recompile sockets and try loading it again
1: RETRY Retry loading FASL for #<ASDF/LISP-ACTION:CL-SOURCE-FILE "iolib/tests" "sockets">.
2: ACCEPT Continue, treating loading FASL for #<ASDF/LISP-ACTION:CL-SOURCE-FILE "iolib/tests" "sockets"> as having been successful.
3: RETRY Retry ASDF operation.
4: CLEAR-CONFIGURATION-AND-RETRY Retry ASDF operation after resetting the configuration.
5: ABORT Give up on "iolib-tests"
6: TOP-LEVEL Return to top level.
Erik, probably the iolib-tests and hyperluminal-mem improvements are not what
you expected from the dead code elimination fix.
Let me know if any new tests are necessary.
Best regards,
- Anton
More information about the armedbear-devel
mailing list