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 | miss-islington, pablogsal, vstinner |
| Date | 2019年06月24日.20:31:37 |
| SpamBayes Score | -1.0 |
| Marked as misclassified | Yes |
| Message-id | <1561408297.94.0.389498998065.issue37359@roundup.psfhosted.org> |
| In-reply-to |
| Content | |
|---|---|
> The issue strikes back: > https://buildbot.python.org/all/#/builders/103/builds/2698 Not good. This build was run after I deployed the new buildbot configuraiton, with the new "cleantest" step, but it has no "cleantest" step. Maybe this job was scheduled before the new configuration was deployed? I rebuilt this build to see if it gets "cleantest" step: https://buildbot.python.org/all/#/builders/103/builds/2701 Note: I'm not surprised that the issue strikes back. It happens all the time with buildbots... |
|
| History | |||
|---|---|---|---|
| Date | User | Action | Args |
| 2019年06月24日 20:31:37 | vstinner | set | recipients: + vstinner, pablogsal, miss-islington |
| 2019年06月24日 20:31:37 | vstinner | set | messageid: <1561408297.94.0.389498998065.issue37359@roundup.psfhosted.org> |
| 2019年06月24日 20:31:37 | vstinner | link | issue37359 messages |
| 2019年06月24日 20:31:37 | vstinner | create | |