Jonathan Turkanis wrote:
As for long running times, I doubled the number of times certain tests are run, with WOULD_BLOCK indicators occuring at different points in each iteration. Still, on my system no test takes more than about two second to run. Most run in less than a second.
Here are my local results:
[...]
I'll try to address the problems reported in this thread, but if they turn out to be specific to Darwin or Linux I may need help. My suggestion is to wait until tomorrow, since some of the testers may have caught Iostreams in an inconsistent state.
Symptoms on Linux: several tests, including bzip2, gzip and newline, get stuck in a busy loop. No system calls are executed in that loop. Waiting won't work, since I'll have to kill the hanging tests manually (for a couple of toolsets). I'll restart the whole test cycle here. Results will get published within 12-24 hours if everything goes well. Regards, m