Message336975
If I can help with testing or builder access or anything just let me know. It appears that I can pretty reliably trigger the error through just the individual tests (test_daemon_threads_shutdown_std{out,err}_deadlock) in isolation, which is definitely less tedious than a full buildbot run to test a change.
BTW, while not directly related since it was only just merged, and I won't pretend to have any real understanding of the changes here, I do have a question about PR 12024 ... it appears HEAD_UNLOCK is used twice in _PyInterpreterState_LookUpID. Shouldn't one of those be HEAD_LOCK? |
|
Date |
User |
Action |
Args |
2019-03-02 00:27:46 | db3l | set | recipients:
+ db3l, nascheme, ncoghlan, vstinner, pmpp, eric.snow, serhiy.storchaka, yselivanov, emilyemorehouse, Johan Dahlin |
2019-03-02 00:27:46 | db3l | set | messageid: <1551486466.8.0.107823056823.issue33608@roundup.psfhosted.org> |
2019-03-02 00:27:46 | db3l | link | issue33608 messages |
2019-03-02 00:27:46 | db3l | create | |
|