Author aeros
Recipients aeros, ned.deily, ronaldoussoren, steve.dower, vstinner
Date 2019-09-05.10:56:34
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1567680995.06.0.316966763421.issue37245@roundup.psfhosted.org>
In-reply-to
Content
It looks like the Azure macOS tests timed out again in the recently opened PR-15688. Specifically, for test_multiprocessing_spawn and test_functools (both of which also timed out in PR-15651, which Victor mentioned earlier):

0:26:41 load avg: 2.89 [418/419/1] test_multiprocessing_spawn crashed (Exit code 1) -- running: test_functools (14 min 38 sec)
Timeout (0:20:00)!

0:32:03 load avg: 3.17 [419/419/2] test_functools crashed (Exit code 1)
Timeout (0:20:00)!

Build logs: https://dev.azure.com/Python/cpython/_build/results?buildId=49868&view=logs&j=18d1a34d-6940-5fc1-f55b-405e2fba32b1

As far as I can tell, PR-15688 should have had no direct influence on test_multiprocessing_spawn or test_functools.

> Maybe macOS on Azure is running slower and we should just increase the timeout?

> Yeah, I agree that increasing the timeout shouldn't be the answer here. 

Since this seems to be affecting multiple PRs, would it be appropriate to attempt to increase the timeout duration as a temporary fix and open an issue for further investigation on the cause of the intermittent slowdown on those tests?
History
Date User Action Args
2019-09-05 10:56:35aerossetrecipients: + aeros, ronaldoussoren, vstinner, ned.deily, steve.dower
2019-09-05 10:56:35aerossetmessageid: <1567680995.06.0.316966763421.issue37245@roundup.psfhosted.org>
2019-09-05 10:56:35aeroslinkissue37245 messages
2019-09-05 10:56:34aeroscreate