[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Monotone-devel] Re: version 1.14 fails "make check"

From: graydon hoare
Subject: [Monotone-devel] Re: version 1.14 fails "make check"
Date: Wed, 04 Aug 2004 11:48:58 -0400
User-agent: Opera M2/7.53 (Linux, build 737)

On 03 Aug 2004 11:41:16 +0200, Peter Simons <address@hidden> wrote:

Well, ... I have reported this error at least TEN TIMES by
now, but if I report it just one more time, maybe it makes a
difference? Here we go again:

I'm sorry for being unresponsive to this; you have indeed
reported it quite a number of times. I'm really sorry, it's
just that while I've seen it myself on my local system, it's
always been a transient fault (1 in 50-ish runs fails to
connect loopback), so I always considered it a race on accept
/ connect, no big deal. mentally I just kept glossing over
your reports.

I've now filed a bug with links to your detailed reports.

 | 22: exchanging work via netsync   FAILED (
 | 26: single manifest netsync       FAILED (

The "make check" process hangs during these tests. I have to
kill the running Monotone process manually for the test case
to proceed. I have had this problem -- as I've said -- for
at least 6 months, if not longer. Only before it just
occurred on "some" machines. Now it occurs on _all_ machines
I try it on.

I know such questions border on rude, but are you sure you have an
otherwise "normal" networking setup? no firewall rules? loopback
connections to otherwise work fine (eg. with netcat)?

alternatively, guessing that it might be a "race which is always
losing" (perhaps my test hardware just fork()s a bit faster than
yours), what happens if you insert a "sleep 5" in between lines
32 and 33 of tests/


reply via email to

[Prev in Thread] Current Thread [Next in Thread]