I've only seen 90 fail once and it was part of a distsign run so I couldn't see what the exact error was. I haven't tried reproducing this one yet on its own.
As to 140, its not an assertion failing but an error being raised inside the etap process relating to sockets. This ends up halting the tests and the last 9 or so weren't being executed. And its a race condition of some sort so its not all that reproducible. I managed to get it fairly often by just rerunning the test by hand many times in quick succession. On Mon, May 2, 2011 at 7:01 AM, Filipe David Manana <[email protected]> wrote: > Hi Paul, > > I can't reproduce those failures on 2 different machines I have > (ThinkPad w/ Linux 32bits and MacBook w/ OS X 32bits). > The assertions that sporadically fail for you are always the same? > Which are them? > > On Fri, Apr 29, 2011 at 12:31 AM, Paul Davis > <[email protected]> wrote: >> In preparing to roll the 1.0.3 release I've noticed a couple etap >> tests failing sporadically. Specifically 090 and 140 have both failed. >> Neither is easy to trigger. 140 at least looks like its related to a >> race condition error on a socket closing somewhere. >> >> Anyone want to look into either of these? >> > > > > -- > Filipe David Manana, > [email protected], [email protected] > > "Reasonable men adapt themselves to the world. > Unreasonable men adapt the world to themselves. > That's why all progress depends on unreasonable men." >
