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 berker.peksag, ezio.melotti, jkloth, martin.panter, serhiy.storchaka, vstinner
Date 2015-09-23.13:27:42
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
"I want this feature to analysis why more and more buildbots fail with a timeout without saying which test was running (well, I suspect multiprocessing tests...)."

Recent example:


[395/399] test_pep352
[396/399] test_ioctl
[397/399] test_multiprocessing_fork
[398/399] test_multiprocessing_forkserver

command timed out: 3900 seconds without output running ['make', 'buildbottest', 'TESTOPTS= -j4', 'TESTPYTHONOPTS=', 'TESTTIMEOUT=3600'], attempting to kill
process killed by signal 9
program finished with exit code -1
Date User Action Args
2015-09-23 13:27:43vstinnersetrecipients: + vstinner, jkloth, ezio.melotti, berker.peksag, martin.panter, serhiy.storchaka
2015-09-23 13:27:43vstinnersetmessageid: <>
2015-09-23 13:27:43vstinnerlinkissue25220 messages
2015-09-23 13:27:42vstinnercreate