2007/3/4, Daniel Johnson wrote:

> [...] Also the recent change to the timeout in test
> 530 doesn't help; now when it fails, it just hangs for 5 minutes
> instead of 30 seconds.

When failing, at least it should help a little bit in finding out what
it is doing in those 5 minutes. Looping around waiting for some
condition that never arrives is different than just blocking at some
point.

Today it seems it has passed all tests. So there is no info of what it
does in those 5 minutes when test 530 or 531 fail.

-- 
-=[Yang]=-