From: Nikodemus S. <nik...@ra...> - 2008-08-14 06:26:41
|
Ooops, forgot to adjust CC. ---------- Forwarded message ---------- From: Nikodemus Siivola <nik...@ra...> Date: Thu, Aug 14, 2008 at 9:25 AM Subject: Re: Test failure of sbcl 1.0.19 with :sb-threads To: Benjamin Lambert <ben...@cm...> Cc: sbc...@li... On Wed, Aug 13, 2008 at 11:49 PM, Benjamin Lambert <ben...@cm...> wrote: > I tried posting a question/bug report to sbcl-help yesterday and again today > to no avail. Is there some other way I can post a question to the sbcl-help > mailing list? You need to subscribe first. sbcl-help is a pretty low-volume list. I'll CC this there, though. > It seems to hang when it gets to: // Running > /home/benlambert/sbcl-1.0.19/tests/timer.impure.lisp, and prints "not ok" > several times. After printing "not ok" 9 times, it hangs. My platform is: > Linux 2.6.9-1.667 x86_64. This is a new one -- thanks for reporting. Anyone else seeing this? * Is your box single or multicore? * If you wait for a minute or two, does the hang resolve itself? * ...if I tell you how, can you try to extract a backtrace from the hung SBCL using GDB? You can run the relevant part of the test suite without other parts using sh run-tests.sh timer.impure.lisp > Is it safe to use this compiled version of SBCL? Yes. That test checks that timers firing in multiple threads at around the same time work correctly. Even though it failing is indicative a bug, unless your code uses asynchronous interrupts or needs parallel timers, there should be little reason to worry about it. > Is it possible to know > which specific test failed? And, can I skip that test to make sure the > remaining tests tun? >From the "not ok" message I can tell which test fails. If you open the file timer.impure.lisp in Emacs, and comment out the #+sb-thread (with-test (:name (:with-timeout :many-at-the-same-time)) ...elided... (assert ok)))) bit, that does the trick. (Adding support for skipping certain tests by name would be nice, if someone is looking for extracurricular SBCL hacking...) Cheers, and thanks for the report! -- Nikodemus Siivola |