On Thu, Jan 28, 2016 at 9:41 PM, Chris Angelico wrote:
> However, as I was doing so (and I just discarded a draft message where
> I'd been typing up notes), my entire system went kerblooie, and I've
> spent the last day rebuilding stuff from scratch. When I get around to
> it,
> After digging through test_socket.py for over an hour (the MRO for
> RecvmsgUDP6Test is enormous!!), I've boiled the issue down to this:
>
> import socket
> MSG = b'asdf qwer zxcv'
> serv = socket.socket(socket.AF_INET6, socket.SOCK_DGRAM)
> serv.bind(("::1", 0))
> cli =
On Thu, Jan 28, 2016 at 7:35 PM, Martin Panter wrote:
> Other things that come to mind are to see if there is anything odd
> about the buildbot’s Linux kernel and glibc versions. Maybe run the
> Python script under “strace” to see if anything strange is going on.
>
I did
2016-01-23 7:03 GMT+01:00 Chris Angelico :
> I just had a major crash on the system that hosts the
> angelico-debian-amd64 buildbot, and as usual, checked it carefully
> after bringing everything up. It seems now to be timing out after an
> hour of operation:
>
>
On Wed, Jan 27, 2016 at 8:39 PM, Victor Stinner
wrote:
> 2016-01-23 7:03 GMT+01:00 Chris Angelico :
>> Running just that test file:
>>
>> $ ./python Lib/test/test_socket.py
>> ... chomp lots of lines ...
>> testRecvmsgPeek (__main__.RecvmsgUDP6Test) ...
On Sun, Jan 24, 2016 at 1:37 AM, Victor Stinner
wrote:
> 3600 seconds is the maximum duration of a single test file. We may reduce it
> since a single test file should not take longer than 30 min. Maybe we can do
> better and put the timeout on a single test function.
3600 seconds is the maximum duration of a single test file. We may reduce
it since a single test file should not take longer than 30 min. Maybe we
can do better and put the timeout on a single test function.
Victor
___
Python-Dev mailing list
On Sat, Jan 23, 2016 at 5:39 PM, Zachary Ware
wrote:
> On Sat, Jan 23, 2016 at 12:03 AM, Chris Angelico wrote:
>> By the way, this looks odd:
>>
>> make buildbottest TESTOPTS= TESTPYTHONOPTS= TESTTIMEOUT=3600
>> in dir
I just had a major crash on the system that hosts the
angelico-debian-amd64 buildbot, and as usual, checked it carefully
after bringing everything up. It seems now to be timing out after an
hour of operation:
On Sat, Jan 23, 2016 at 12:03 AM, Chris Angelico wrote:
> By the way, this looks odd:
>
> make buildbottest TESTOPTS= TESTPYTHONOPTS= TESTTIMEOUT=3600
> in dir /root/buildarea/3.x.angelico-debian-amd64/build (timeout 3900 secs)
>
> The parameter says 3600 (which corresponds to
10 matches
Mail list logo