[issue37245] Azure Pipeline 3.8 CI: multiple tests hung and timed out on macOS 10.13

STINNER Victor added the comment: It seems like macOS job pass again on Azure Pipelines. I close the issue. -- resolution: -> fixed stage: -> resolved status: open -> closed ___ Python tracker

[issue37245] Azure Pipeline 3.8 CI: multiple tests hung and timed out on macOS 10.13

Steve Dower added the comment: Filed as issue38084 I recommend not investigating this issue any further until that one is resolved. -- ___ Python tracker ___

[issue37245] Azure Pipeline 3.8 CI: multiple tests hung and timed out on macOS 10.13

STINNER Victor added the comment: Steve: Would you mind to open a separated issue for the multiprocessing bug? multiprocessing is supposed to handle this case. -- ___ Python tracker

[issue37245] Azure Pipeline 3.8 CI: multiple tests hung and timed out on macOS 10.13

Steve Dower added the comment: I suspect this code is a repro - it certainly locks up the host process reliably enough. Perhaps if we unblock multiprocessing in the context of a crashed worker then it'll show what the underlying errors are? import os from multiprocessing import Pool def f

[issue37245] Azure Pipeline 3.8 CI: multiple tests hung and timed out on macOS 10.13

Kyle Stanley added the comment: 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]

[issue37245] Azure Pipeline 3.8 CI: multiple tests hung and timed out on macOS 10.13

Ned Deily added the comment: Yeah, I agree that increasing the timeout shouldn't be the answer here. I still have never seen failure modes like this when running my own tests. The idea about CPUs is one worth pursuing although I usually run with -j3. Also I wonder how much memory the VM is

[issue37245] Azure Pipeline 3.8 CI: multiple tests hung and timed out on macOS 10.13

Steve Dower added the comment: > Maybe macOS on Azure is running slower and we should just increase the > timeout? (Aside, why don't the macOS buildbots have a tag saying that? Took me ages to find them...) I doubt it's running 6-7x slower. More likely something is causing one of the worke

[issue37245] Azure Pipeline 3.8 CI: multiple tests hung and timed out on macOS 10.13

STINNER Victor added the comment: > I'm still seeing this, maybe 1 in 20 builds, so it's semi-random. A new > deadlock, maybe? It seems like only the jobs on Azure are killed by timeout. The jobs on macOS buildbots look fine. Maybe macOS on Azure is running slower and we should just increas

[issue37245] Azure Pipeline 3.8 CI: multiple tests hung and timed out on macOS 10.13

Steve Dower added the comment: I'm still seeing this, maybe 1 in 20 builds, so it's semi-random. A new deadlock, maybe? -- nosy: +steve.dower ___ Python tracker ___ _

[issue37245] Azure Pipeline 3.8 CI: multiple tests hung and timed out on macOS 10.13

Ned Deily added the comment: FWIW, I tried reproducing with 3.8 at 996e52623af3854552d41751e0c2522bc0a7e84f (the PR 14000 checkin) on both a current 10.14.5 Mojave system and on a 10.13.6 High Sierra system (the version used in the failed Azure test) and did not see any unusual failures. I