[issue36342] test_venv failure when executed by test_multiprocessing and the platform lacks a functional sem_open()

STINNER Victor added the comment: It seems like this issue has been fixed in the master branch. Reopen the issue if you consider that the fix should be backported. -- resolution: -> fixed stage: patch review -> resolved status: open -> closed ___

[issue36342] test_venv failure when executed by test_multiprocessing and the platform lacks a functional sem_open()

miss-islington added the comment: New changeset 5437ccca1424e415a938c583df43d8cc74047d16 by Miss Islington (bot) (xdegaye) in branch 'master': bpo-36342: Fix test_multiprocessing in test_venv (GH-12513) https://github.com/python/cpython/commit/5437ccca1424e415a938c583df43d8cc74047d16 --

[issue36342] test_venv failure when executed by test_multiprocessing and the platform lacks a functional sem_open()

Change by Xavier de Gaye : -- keywords: +patch pull_requests: +12464 stage: -> patch review ___ Python tracker ___ ___ Python-bugs-

[issue36342] test_venv failure when executed by test_multiprocessing and the platform lacks a functional sem_open()

Xavier de Gaye added the comment: Removing the bpo-35978 dependency as changeset 8bba81fd55873148c65b7d0e6a6effbd63048c76 that fixes bpo-35978 only skips test_multiprocessing when test_venv is run from a venv. -- dependencies: -test_venv fails in Travis with GCC ___

[issue36342] test_venv failure when executed by test_multiprocessing and the platform lacks a functional sem_open()

Brett Cannon added the comment: I guess my confusion comes from the fact that test_venv in isolation is a totally fine test suite, it just fails when test_multiprocessing runs it due to something multiprocessing-related. I've tried tweaking the title to reflect the fact that it's a test_venv