STINNER Victor added the comment:

> Too bad, test_resize() failed again while testing commit 
> 56e162ad5c5d3effe9b4f05d0179e1b6a2a2d9b8 :-( So this fix was not enough.

I am not sure anymore about this statement. I had a bug in my watchdog code, 
that I fixed after this failure.

I ran again the test during 3 hours and it didn't fail.

I reverted all my local changes, I rebuild Python 2.7 in debug mode to get a 
fresh python_d.exe, I removed all __pycache__, and then I ran again the test 
during 1 hour: no fail. I ran 4 instances of the test in parallel during 1 
hour: no fail.

Hum, it *seems* like the bug was fixed.

Since it's a race condition, it's not possible to say that it's really fixed. 
But my test results show that the bug is very likely to be fixed, so I close 
the bug.

I will watch AMD64 Windows8.1 Refleaks 2.7 buildbot slave next days to check if 
the bug occurs again.

----------
resolution:  -> fixed
stage:  -> resolved
status: open -> closed

_______________________________________
Python tracker <rep...@bugs.python.org>
<http://bugs.python.org/issue31068>
_______________________________________
_______________________________________________
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

Reply via email to