[phobos] State of std.parallelism unit tests
David Simcha
dsimcha at gmail.com
Fri Jun 3 05:53:23 PDT 2011
Ok, I'm running the main unit test in a loop in a debugger right now
trying to reproduce this thing. 64-bit Ubuntu, 64-bit DMD, building
64-bit binary, release mode. So far I've been through ~175 runs and
have nothing but successes. Can you give me a rough percentage of the
time that it fails for you?
One thing you could do to help is to do basically the same thing I'm
doing but on your setup. Execute the main unit test in a loop (just put
a loop around the whole thing) inside GDB. If/when it crashes, send me
a backtrace of all the threads (thread apply all bt), the register info
(info registers) and the disassembly of the function where it crashed
(disass).
On 6/3/2011 3:05 AM, Jonathan M Davis wrote:
> On 2011-06-02 23:52, Jonathan M Davis wrote:
>> On 2011-06-02 06:30, David Simcha wrote:
>>> Thanks. A second look with fresher eyes revealed a subtle but serious
>>> bug in the ResubmittingTasks base mixin (which affects parallel foreach,
>>> map and amap) and a relatively minor corner-case bug in reduce(). Both
>>> were introduced after the 2.053 release as a result of over-aggressive
>>> optimizations. I've checked in fixes for these. I'm not sure whether
>>> they're the root cause of the issues you're seeing, though. If it's not
>>> too much work, please try to reproduce your bugs again.
>> Well, I have yet to see the failure again. Unfortunately, that doesn't
>> guarantee anything given the intermittent nature of the failure, but I
>> think that there's a good chance that it's been fixed. I'll post about it
>> if it happens again, but I think that for the moment, we can assume that
>> it's been fixed.
> I take that back. It just happened again. The std.parallelism tests
> segfaulted.
>
> - Jonathan M Davis
> _______________________________________________
> phobos mailing list
> phobos at puremagic.com
> http://lists.puremagic.com/mailman/listinfo/phobos
>
More information about the phobos
mailing list