On Tue, 2015-01-27 at 09:46 -0500, Rafael Schloming wrote: > Do you have tracing turned on when they time out? With the protocol trace > enabled the tests slow down enough that some of them don't finish before > the various timeouts kick in.
Much more insidious. It turns out that if you use 0.0.0.0 as a connect address AND you have a VPN running AND you are using jython then things hang (at least on fedora 20 in my house in January.) Looking up the ip(7) man page it seems like 0.0.0.0 is only supposed to be used as a bind address, not a connect address, so I switched the tests in question to use 127.0.0.1 and everything works (it also works if I turn off my VPN or use proper python) I didn't switch everything in python to use 127.0.0.1 for connect (NOTE 0.0.0.0 is still correct for listening) in case there was some hidden disaster there. Probably at least the examples and maybe the default port for class Url should be changed, any dissent? > --Rafael > > On Tue, Jan 27, 2015 at 9:29 AM, Alan Conway <[email protected]> wrote: > > > On Tue, 2015-01-27 at 09:00 -0500, Rafael Schloming wrote: > > > Hi Alan, > > > > > > The recently added stuff in utils.py seems to have broken the java build. > > > It uses the 'with' keyword which is apparently not supported in jython. > > > > > > --Rafael > > > > Fixing ASAP. I have persistent trouble with the java test failing with > > timeouts I need to figure that out and stop skipping them :( > > > > > >
