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 lys.nikolaou, pablogsal, vstinner, zach.ware
Date 2020-09-08.09:19:11
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1599556751.33.0.978624915444.issue41741@roundup.psfhosted.org>
In-reply-to
Content
> Making the timeout bigger can be a possibility, certainly, but this also means the builder will get stuck more time in race conditions or deadlocks :(

Race conditions and deadlocks are less likely than false alarms of builds failed because the timeout is too short.

So far, I'm only aware of this specific buildbot worker which is too slow for "(timeout: 25 min, worker timeout: 30 min)". So just increase the timeout to 40 min, no?
History
Date User Action Args
2020-09-08 09:19:11vstinnersetrecipients: + vstinner, zach.ware, lys.nikolaou, pablogsal
2020-09-08 09:19:11vstinnersetmessageid: <1599556751.33.0.978624915444.issue41741@roundup.psfhosted.org>
2020-09-08 09:19:11vstinnerlinkissue41741 messages
2020-09-08 09:19:11vstinnercreate