Thanks for letting me know. I have no idea why this is happening. I was seeing some weirdness on FreeBSD only, but I gave up trying to solve that until the FreeBSD port is more stable or I can reproduce it on some other OS. I've run the unittests for std.parallelism on my (old) Athlon 64 X2 tens of thousands of times on Linux 64 without any issues, so unfortunately this is going to be hard to debug. Two questions:
1. Does it happen on the latest Git version or on the 2.053 release version? 2. Could you try to figure out which test is failing? On Sat, May 28, 2011 at 9:34 PM, Jonathan M Davis <[email protected]>wrote: > I was wondering what the current state of the std.paralellism unit tests > is. > Everything is green on the autotester. And when they run properly, they > pass > on my system. But I find that they frequently freeze after printing out > > totalCPUs = 6 > > (I have a 6-core Phenom II), and when they don't freeze, a segfault occurs > at > least some of the time. I'm running a pure 64-bit build stack (dmd, > druntime, > and Phobos are all 64-bit) on Linux. Is this expected at all? Should I do > anything to try and track this down? I'm not actually using std.paralellism > at > the moment, so it doesn't really impact me beyond the irritation with the > unit > tests, but if there's a bug, then obviously it needs to be dealt with. Is > this > well-known, or is it something that I should be reporting? David, what is > the > situation with this? > > - Jonathan M Davis > _______________________________________________ > phobos mailing list > [email protected] > http://lists.puremagic.com/mailman/listinfo/phobos >
_______________________________________________ phobos mailing list [email protected] http://lists.puremagic.com/mailman/listinfo/phobos
