➜

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 aeros
Recipients aeros, corona10, pitrou, tomMoral, vstinner
Date 2020-04-29.03:00:37
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1588129237.59.0.319816602011.issue39995@roundup.psfhosted.org>
In-reply-to
Content 
I am a bit concerned about the performance implication of accessing the thread wakeup through a lock in the call queue, but for now I think it's reasonable to address the buildbot failure with a locking solution while we try to find a better one.

I'm not certain if we'll be able to find one that correctly addresses the failures with zero additional locking, but I think we may be able to reduce the number of times we use the lock compared to the implementation in GH-19760. I'll spend some time exploring that as I find the time to, and report back with any significant findings.
History
Date User Action Args
2020-04-29 03:00:37aerossetrecipients: + aeros, pitrou, vstinner, tomMoral, corona10
2020-04-29 03:00:37aerossetmessageid: <1588129237.59.0.319816602011.issue39995@roundup.psfhosted.org>
2020-04-29 03:00:37aeroslinkissue39995 messages
2020-04-29 03:00:37aeroscreate