#208 closed defect (fixed)

unit test failure on cygwin

Reported by: zooko Owned by: nobody
Priority: major Milestone: 0.7.0
Component: unknown Version: 0.7.0
Keywords: Cc:
Launchpad Bug:


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

Change History (3)

comment:1 Changed at 2007-11-14T21:05:40Z by warner

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.

comment:2 Changed at 2007-11-19T17:48:02Z by warner

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.

comment:3 Changed at 2007-11-19T19:27:23Z by zooko

  • Resolution set to fixed
  • Status changed from new to closed
Note: See TracTickets for help on using tickets.