STINNER Victor added the comment:
Oh, I missed your second message: "So, I guess "flacky". Cannot reproduce in
any case."
So well, I close the issue. It's ok, sometimes things break randomly :-) The
important thing is that the current status is that tests pass ;-)
--
resolution:
STINNER Victor added the comment:
Since build 2389 which failed, 21 builds succeeded. The failure looks random,
so I success to close the issue. I leave it open since it seems like Michael
Felt is interested to investigate ;-)
--
___
Python
Michael Felt added the comment:
On 12/04/2019 10:28, Michael Felt wrote:
> Michael Felt added the comment:
>
> On 10/04/2019 18:49, STINNER Victor wrote:
>> STINNER Victor added the comment:
>>
>> "I am looking into this - but as it seems to have gone away again - is
>> there a simple way to
Michael Felt added the comment:
On 10/04/2019 18:49, STINNER Victor wrote:
> STINNER Victor added the comment:
>
> "I am looking into this - but as it seems to have gone away again - is
> there a simple way to get that code back, and/or see what the diff is,
> before/badrun/after?"
>
> Maybe
STINNER Victor added the comment:
"I am looking into this - but as it seems to have gone away again - is
there a simple way to get that code back, and/or see what the diff is,
before/badrun/after?"
Maybe it's just a flacky test. It's hard to guess.
You can get the Git revision of a build by
Michael Felt added the comment:
On 09/04/2019 18:51, STINNER Victor wrote:
> New submission from STINNER Victor :
>
> https://buildbot.python.org/all/#/builders/10/builds/2389
>
> 0:45:36 [412/420/1] test_venv crashed (Exit code 1)
> Timeout (0:15:00)!
> Thread 0x0001 (most recent call
New submission from STINNER Victor :
https://buildbot.python.org/all/#/builders/10/builds/2389
0:45:36 [412/420/1] test_venv crashed (Exit code 1)
Timeout (0:15:00)!
Thread 0x0001 (most recent call first):
File
