[phobos] State of std.parallelism unit tests

[David Simcha]

On 6/3/2011 6:43 PM, Jonathan M Davis wrote:
> On 2011-06-03 15:24, David Simcha wrote:
>> Ok, I left the unit tests running in a loop on my home computer all day
>> while I was at work. They ran about 13,000 times without failing once.
>> Something about your setup is enabling the failures or at least making
>> them drastically more likely.
> Well, unfortunately, this does seem to be one of those modules where a
> difference in CPU or architecture can have a large impact on behavior. In any
> case, I'll look at setting up the tests to run in a loop and see how well they
> do. And I guess that I'll have to spend some time debugging std.parallelism to
> at least figure out exactly _what_ is causing a segfault, though I question
> that I'll be able to actually fix the problem without spending a considerable
> amount of time learning how std.parallelism works.

I'd sincerely appreciate if you did this.  If you could tell me 
specifically where the problem is, there's a decent chance I could 
figure it out just by reading the code carefully, especially if I got a 
full stack trace, disassembly and registers.