On Sat, 2013-03-23 at 04:24 +0400, Anton Vodonosov wrote:
19.03.2013, 00:42, "Stelian Ionescu" sionescu@cddr.org:
I'd like to make a new release by this weekend, so please run the test suite on all available implementations.
I have run the tests on the following implementations*
- implementation names are computed by (asdf:implementation-identifier); ecl-12.12.1-unknown means the ECL 12.12.1 release, don't be confused by the "unknown' word.
Windows: sbcl-1.1.0.45-win-x86 OK sbcl-1.1.0.36.mswinmt.1201-284e340-win-x64 OK sbcl-1.1.0.36.mswinmt.1201-284e340-win-x86 OK abcl-1.1.0-fasl39-win-x64 HANGS ccl-1.8-f95-win-x86 OK ccl-1.8-f95-win-x64 OK ecl-12.12.1-ab933fa5-win-x86-bytecode FAILED-TESTS: bordeaux-threads-test.join-thread-return-value bordeaux-threads-test.current-thread-identity ecl-12.12.1-ab933fa5-win-x86-lisp-to-c FAILED-TESTS bordeaux-threads-test.join-thread-return-value bordeaux-threads-test.current-thread-identity bordeaux-threads-test.default-special-bindings bordeaux-threads-test.should-retrieve-thread-name bordeaux-threads-test.condition-variable bordeaux-threads-test.should-identify-threads-correctly bordeaux-threads-test.should-have-thread-interaction bordeaux-threads.interrupt-thread acl-9.0a-win-x86 OK
Linux: ccl-1.8-f95-linux-x86 OK ccl-1.9-f96-linux-x86 HANGS (not alwasy 2 times from 4 tries) sbcl-1.1.1-linux-x86 OK sbcl-1.1.3.12-b9691ef-linux-x86 OK cmu-snapshot-2013-03-a__20d_unicode_-linux-x86 HANGS (the issue I reported some time ago, it hangs and keeps printing lot of '.' symbols to the log) ecl-12.12.1-unknown-linux-x86-bytecode OK ecl-12.12.1-unknown-linux-x86-lisp-to-c FAILED-TESTS bordeaux-threads-test.join-thread-return-value bordeaux-threads-test.should-identify-threads-correctly bordeaux-threads.interrupt-thread bordeaux-threads-test.default-special-bindings bordeaux-threads-test.should-retrieve-thread-name bordeaux-threads-test.condition-variable bordeaux-threads-test.current-thread-identity bordeaux-threads-test.should-have-thread-interaction abcl-1.1.1-fasl39-linux-x86" HANGS
Thanks for the testing. I only use Linux/x86_64. I can reproduce the ABCL issue and I've notified its developers, but not the ones with CCL - I tried both 32bit and 64bit for many times without problems - nor with CMUCL, so I need more information. Can you interrupt the test and get stack traces ? As for ECL, I can't even compile it, I'll just report the problem. .