On 06.01.2014 08:09, Chris Angelico wrote:
Then further down, several SSL tests attempt:
s.connect_ex((svn.python.org, 444)))
and get back EAGAIN when they're expecting ECONNREFUSED. Possibly my
firewall's delaying things somewhat and it's timing out with a signal;
when I try manually, the
On Mon, Jan 6, 2014 at 7:11 PM, Christian Heimes christ...@python.org wrote:
On 06.01.2014 08:09, Chris Angelico wrote:
Then further down, several SSL tests attempt:
s.connect_ex((svn.python.org, 444)))
and get back EAGAIN when they're expecting ECONNREFUSED. Possibly my
firewall's
On 06.01.2014 09:22, Chris Angelico wrote:
No, it's Debian Wheezy inside Debian Wheezy; though the outer system
is a somewhat messy one (I installed Wheezy before it was stable, and
compiled my own ALSA drivers and a few other things).
But it could well be that same issue, as it seems to
On Mon, Jan 6, 2014 at 7:58 PM, Christian Heimes christ...@python.org wrote:
Interesting, maybe it's a general NAT issue? So far I have seen the issue on
Windows only. What kind of VM are you using? I'm using virtualbox for my
Windows VMs.
It's Oracle VirtualBox v4.2.20 r90963.
Just backport
On Mon, Jan 6, 2014 at 2:09 AM, Chris Angelico ros...@gmail.com wrote:
The first build my new root buildbot did showed errors in the 2.7 test
suite, but I thought little of it as quite a few other 2.7 buildbots
are showing red, too. But it seems they're showing different errors,
so there
The first build my new root buildbot did showed errors in the 2.7 test
suite, but I thought little of it as quite a few other 2.7 buildbots
are showing red, too. But it seems they're showing different errors,
so there might be something wrong with the setup.
