[armedbear-devel] Bordeaux-threads test hangs

[Anton Vodonosov]

25.03.2013, 14:03, "Mark Evenson" <evenson at panix.com>:
> On 3/24/13 2150 , Erik Huelsmann wrote:
>
>>   From a mail by Stellian Ionescu:
>>
>>  From: Stelian Ionescu <sionescu at cddr.org <mailto:sionescu at cddr.org>>
>>  To: armedbear-devel at common-lisp.net <http://common-lisp.net>
>>  Cc:
>>  Date: Sat, 23 Mar 2013 01:07:04 +0000 (UTC)
>>  Subject: Bordeaux-threads test hangs
>>  The B-T test suite hangs on test "condition-variable". If I do a ^C ABCL
>>  exits,
>>  so I'm not sure how to debug it.
>>
>>  CL-USER(1): (lisp-implementation-version)
>>  "1.1.1"
>>  "OpenJDK_64-Bit_Server_VM-Oracle_Corporation-1.7.0_17-b02"
>>  "amd64-Linux-3.7.10-10-default"
>
> Even through I swear I ensured that BORDEAUX-THREADS always works before
> making releases, I have reproduced the problem on abcl-1.1.1 onwards,
> but it doesn't occur in abcl-1.1.0.  I am about to kick of a bisect
> regression to figure out where this broke.
>
> Filed as [ticket][312].
>
> [1]: http://trac.common-lisp.net/armedbear/ticket/312
>

Mark, the test hangs not always.

I think this is bug in the test, because the test is not guaranteed to work.

It create 100 threads, each thread waits for (= i *shared*). In every thread i has different
value, from 0 to 99. So the threads are chained and each thread
waits white the previous one will increase *shared*.

But the threads use bt:condition-notify to interact, which deliver
notification to only one of the waiting thread, and there is not guarantee
it will be right thread.

The tests passes on SBCL. Maybe SBCL always choses to notify
the first thread in the waiting queue.

But bt:condition-notify contract does not require this.

In short, I think what we see is not a bug in ABCL or bordeaux-threads,
but a bug in the test.

Best regards,
- Anton