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 cagney
Recipients bquinlan, cagney, hroncok, hugh, josh.r, jwilk, pablogsal, pitrou, vstinner
Date 2019-04-15.14:30:08
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1555338609.12.0.279785396461.issue35866@roundup.psfhosted.org>
In-reply-to
Content
@hroncok see comment msg339370

Vanilla 3.7.0 (re-confirmed) didn't contain the change, nor did 3.6.8 (ok, that isn't vanilla) but both can hang using the test.  It can take a while and, subjectively, it seems to depend on machine load.  I've even struggled to get 3.7.3 to fail without load.

Presumably there's a race and grinding the test machine into the ground increases the odds of it happening.

The patch for bpo-6721 could be causing many things, but two to mind:

- turning this bug into bpo-36533 (aka bpo-6721 caused a regression)
- slowed down the fork (sending time acquiring locks) which increased the odds of this hang

My hunch is the latter as the stack dumps look nothing like those I analyzed for bpo-36533 (see messages msg339454 and msg339458).
History
Date User Action Args
2019-04-15 14:30:09cagneysetrecipients: + cagney, bquinlan, pitrou, vstinner, jwilk, josh.r, hroncok, pablogsal, hugh
2019-04-15 14:30:09cagneysetmessageid: <1555338609.12.0.279785396461.issue35866@roundup.psfhosted.org>
2019-04-15 14:30:09cagneylinkissue35866 messages
2019-04-15 14:30:08cagneycreate