[issue45128] test_multiprocessing fails sporadically on the release artifacts

STINNER Victor added the comment: I can still reproduce the issue if test_logging.py is simplified to: --- import unittest import sys class LogRecordTest(unittest.TestCase): def test_multiprocessing(self): import multiprocessing.queues del sys.modules['multiprocessing']

[issue45128] test_multiprocessing fails sporadically on the release artifacts

STINNER Victor added the comment: Minimum command to reproduce the issue (on Linux): $ ./python -m test -m test.test_logging.LogRecordTest.test_multiprocessing test_genericalias test_logging test_multiprocessing_fork -v (...) 0:00:00 load avg: 0.45 Run tests sequentially 0:00:00 load avg: 0.

[issue45128] test_multiprocessing fails sporadically on the release artifacts

STINNER Victor added the comment: > The thing is that we are running the test suite constantly on CI and > buildbots and non of them have seen this problem :( Most (if not all) Python CIs run the Python test suite using -jN option which runs each test in isolation: a fresh process is spawned

[issue45128] test_multiprocessing fails sporadically on the release artifacts

Pablo Galindo Salgado added the comment: > but quite reliably does occur (three times in three different spots) if the > whole test suite is executed: The thing is that we are running the test suite constantly on CI and buildbots and non of them have seen this problem :( We should see if we

[issue45128] test_multiprocessing fails sporadically on the release artifacts

Alexander Kanavin added the comment: I am seeing this one too in my yocto builds of 3.10rc2. What is bizarre is that the issue does not occur if the multiprocessing test is run in isolation: python3 -m test -v test_multiprocessing_fork but quite reliably does occur (three times in three diff

[issue45128] test_multiprocessing fails sporadically on the release artifacts

STINNER Victor added the comment: I'm not sure if unittest.mock code to import the module is reliable: see bpo-39551. It imports "multiprocessing", use getattr() to get multiprocessing.shared_memory. If getattr() fails with AttributeError, it tries to import "mulitprocessing.shared_memory",

[issue45128] test_multiprocessing fails sporadically on the release artifacts

STINNER Victor added the comment: I guess that the test was previously skipped, and bpo-45042 enabled again the test: commit e5976dd2e6e966183da59df99978ebcb4b3a32df Author: Miss Islington (bot) <31488909+miss-isling...@users.noreply.github.com> Date: Sat Sep 4 14:04:44 2021 -0700 bpo-

[issue45128] test_multiprocessing fails sporadically on the release artifacts

Nikita Sobolev added the comment: Related issues: - https://bugs.python.org/issue45042 - https://bugs.python.org/issue45052 -- nosy: +sobolevn ___ Python tracker ___ _

[issue45128] test_multiprocessing fails sporadically on the release artifacts

New submission from Pablo Galindo Salgado : While testing the release artifacts I encountered this failure: test test_multiprocessing_fork failed -- Traceback (most recent call last): File "/tmp/tmpu30qfjpr/installation/lib/python3.10/unittest/mock.py", line 1239, in _dot_lookup return g