This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author vstinner
Recipients paul.moore, pitrou, steve.dower, tim.golden, vstinner, zach.ware
Date 2017-07-04.10:00:01
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1499162402.16.0.716183335751.issue29796@psf.upfronthosting.co.za>
In-reply-to
Content
Oh wow! The commit 1fef0154d97bd7f01c5bc59954a278bacf1a3f0e fixed PGO compilation on Python 2.7: http://buildbot.python.org/all/builders/AMD64%20Debian%20PGO%202.7/builds/227 is the first successful build since June 20. I didn't notice that the PGO buildbot was also stuck in running test_weakref in the compile step: job killed after 30 min.
---
...
0:06:01 [380/400] test_warnings
0:06:02 [381/400] test_wave
0:06:02 [382/400] test_weakref

command timed out: 1200 seconds without output running ['make', 'all'], attempting to kill
process killed by signal 9
program finished with exit code -1
elapsedTime=1699.111100
---

While build 206 was green, the buildbot started to fail in build 207:

http://buildbot.python.org/all/builders/AMD64%20Debian%20PGO%202.7/builds/207

The strange thing is that this change only contains two small changes:
* commit b39a7481ee7e6166d6d2b252a7a514b1f6553dfa
* commit d4324baca4c03eb8d55446cd1b74b32ec5633af5

I fail to understand how these changes make test_weakref hangs.

Well, at least the good news is that it's now fixed ;-)
History
Date User Action Args
2017-07-04 10:00:02vstinnersetrecipients: + vstinner, paul.moore, pitrou, tim.golden, zach.ware, steve.dower
2017-07-04 10:00:02vstinnersetmessageid: <1499162402.16.0.716183335751.issue29796@psf.upfronthosting.co.za>
2017-07-04 10:00:02vstinnerlinkissue29796 messages
2017-07-04 10:00:01vstinnercreate