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 | trent |
|---|---|
| Recipients | loewis, nnorwitz, trent |
| Date | 2008年04月10日.22:55:25 |
| SpamBayes Score | 0.006139572 |
| Marked as misclassified | No |
| Message-id | <1207868126.69.0.898204218113.issue2611@psf.upfronthosting.co.za> |
| In-reply-to |
| Content | |
|---|---|
It'd be nice if there was a facility to force a particular test to be re-run in verbose mode with the most recent build via the buildbot web interface. It would allow us to get a bit more information about what's going on when the buildbots report stuff like this: test_property test_cprofile test_signal command timed out: 1800 seconds without output, killing pid 214235 SIGKILL failed to kill process using fake rc=-1 program finished with exit code -1 Neal or Martin, if neither of you have the desire/bandwidth to look into this, I'm more than happy to take it on. Suspect it'd involve a buildbot change on dinsdale right? |
|
| History | |||
|---|---|---|---|
| Date | User | Action | Args |
| 2008年04月10日 22:55:27 | trent | set | spambayes_score: 0.00613957 -> 0.006139572 recipients: + trent, loewis, nnorwitz |
| 2008年04月10日 22:55:26 | trent | set | spambayes_score: 0.00613957 -> 0.00613957 messageid: <1207868126.69.0.898204218113.issue2611@psf.upfronthosting.co.za> |
| 2008年04月10日 22:55:25 | trent | link | issue2611 messages |
| 2008年04月10日 22:55:25 | trent | create | |