El 18 d’abril de 2012 15:46, Steven Chamberlain ha escrit:
> With it, I hit a tst-timer5 regression during build.
Don't worry about tst-timer5, it's a fake regression. Previously it
"succeeded" by exitting without testing anything.
> On 18/04/12 07:02, Petr Salinger wrote:
> - if (terminated
On 18/04/12 14:46, Steven Chamberlain wrote:
> And in the ruby1.9.1 test suite, test_io looks like it might be fixed by
> this, but test_thread still hangs sometimes.
Cancel that part... ruby1.9.1's test_io still fails sometimes,
especially if I run it without -v, so nothing has changed there.
R
On 18/04/12 03:39, Steven Chamberlain wrote:
> Strange, the workaround hasn't really changed anything for me on
> kfreebsd-i386
Sorry that was wrong, I had dry-run the patch without actually applying
it :(
With it, I hit a tst-timer5 regression during build.
But if I keep the timeout at its def
On 16/04/12 22:08, Robert Millan wrote:
> If I hit ^Z, poll is interrupted, then "fg" makes it progress. By
> doing this a couple of times I managed to make test_socket finish.
> Alternatively, I patched glibc with this workaround (see attachment).
> This makes the test finish in about 16 seconds.
Hi,
I found something about test_socket hang. The problem I'm seeing
looks like a race condition. kdump -H yields:
73334 100505 python CALL thr_kill(0x1884e,SIG(null))
73334 100505 python RET thr_kill 0
73334 100505 python CALL thr_exit(0xccab78)
73334 100430 python
5 matches
Mail list logo
