| Summary: | [lisp overlay] dev-lisp/sbcl-1.1.6-r2 - 1 out of 25 total tests failed: SB-CONCURRENCY-TEST::FRLOCK.1. | ||
|---|---|---|---|
| Product: | Gentoo Linux | Reporter: | Steven Trogdon <strogdon> |
| Component: | Current packages | Assignee: | Gentoo Lisp Project <lisp> |
| Status: | RESOLVED DUPLICATE | ||
| Severity: | normal | ||
| Priority: | Normal | ||
| Version: | unspecified | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Package list: | Runtime testing required: | --- | |
| Attachments: | build log | ||
|
Description
Steven Trogdon
2013-04-11 17:45:28 UTC
(You can set FEATURES=test-fail-continue to make test phase failures non-fatal.) (In reply to comment #1) > (You can set FEATURES=test-fail-continue to make test phase failures > non-fatal.) I'm unable to get this to work here. Perhaps because the failure is not associated with the testsuite under the test/ folder by with some tests embedded in subfolders under the contrib/ folder. I'm not sure how to disable these tests. Perhaps this an upstream issue? See https://bugs.launchpad.net/sbcl/+bug/1087955 Adding sed "s:with-timeout 60:with-timeout 240:g" -i contrib/sb-concurrency/tests/test-frlock.lisp || die to src_prepare() seemed to cure things. I had tried timeouts of 90 and 120 without success. So maybe the hardware is too slow. I met the similar problem: I got stuck at "
Doing 25 pending tests of 25 tests total.
Test SB-CONCURRENCY-TEST::FRLOCK.1 failed
Form: (HANDLER-CASE
(WITH-TIMEOUT 60
(SB-CONCURRENCY-TEST::TEST-FRLOCKS))
(TIMEOUT (SB-CONCURRENCY-TEST::C) (ERROR "~A" SB-CONCURRENCY-TEST::C)))
Expected values: NIL
NIL
Actual value: #<SIMPLE-ERROR "~A" {1003C34423}>.
SB-CONCURRENCY-TEST::QUEUE.1 SB-CONCURRENCY-TEST::QUEUE.2
SB-CONCURRENCY-TEST::QUEUE.3 SB-CONCURRENCY-TEST::QUEUE.4
"
There would be 30 threads running and kick you out of your system.
But I build sbcl successfully on another computer and laptop.
Finally I figure out that's because I was using gcc 4.8.0.
Change back to gcc 4.7.2 and a older version kernel(3.6.11-r1) seems to
solve this problem.
*** This bug has been marked as a duplicate of bug 468482 *** |