tahoe-lafs/trac-2024-07-25

unit test failure on cygwin #208

New issue

Closed

opened 2007-11-14 14:52:31 +00:00 by zooko · 2 comments

zooko commented

2007-11-14 14:52:31 +00:00

Owner

The unit tests on the cygwin buildslave are failing. The waterfall suggests that they started failing on patch changeset:5e974ede20b1bae4, but that makes no sense.

tahoe-lafs added the

labels 2007-11-14 14:52:31 +00:00

tahoe-lafs added this to the 0.7.0 milestone 2007-11-14 14:52:31 +00:00

warner commented

2007-11-14 21:05:40 +00:00

Author

Owner

The test will fail if the first node has not finished shutting down by the
time the second node starts, because the node will re-use the TCP port
number, and if the first node is still running, the second node will be
unable to grab the same port.

On windows, it appears that either we do not have a good handle on when the
first node has finished shutting down. I remember putting an arbitrary delay
(2 seconds?) in there to improve the isolation, but obviously that only works
if the machine is not heavily loaded and can complete its shutdown in time.

I recall that the fix wasn't trivial, because I've already put half a day of
effort into fixing this one and wasn't able to figure it out.

if I recall correctly, this test failure involves staring a node, shutting it down, waiting for a moment, then starting it back up again. The test is intended to make sure that the state created by the first incarnation is usable by the second. The test will fail if the first node has not finished shutting down by the time the second node starts, because the node will re-use the TCP port number, and if the first node is still running, the second node will be unable to grab the same port. On windows, it appears that either we do not have a good handle on when the first node has finished shutting down. I remember putting an arbitrary delay (2 seconds?) in there to improve the isolation, but obviously that only works if the machine is not heavily loaded and can complete its shutdown in time. I recall that the fix wasn't trivial, because I've already put half a day of effort into fixing this one and wasn't able to figure it out.

warner commented

2007-11-19 17:48:02 +00:00

Author

Owner

I put in an extra delay on this test.. it looks like the delay I put in earlier was in the wrong place. It remains to be seen whether this is a stable fix or not.

tahoe-lafs added the

fixed

label 2007-11-19 19:27:23 +00:00

zooko closed this issue

2007-11-19 19:27:23 +00:00