diff options
author | Miss Islington (bot) <31488909+miss-islington@users.noreply.github.com> | 2019-07-11 18:38:37 (GMT) |
---|---|---|
committer | GitHub <noreply@github.com> | 2019-07-11 18:38:37 (GMT) |
commit | 3d58b78481e0238593f85cc182b798fe3b77648c (patch) | |
tree | 1bb6e5f60d39f1dcd92e7c08394cc36f5c28cfec | |
parent | 107171500d7d6e60f463eeb4db492c0ae292a669 (diff) | |
download | cpython-3d58b78481e0238593f85cc182b798fe3b77648c.zip cpython-3d58b78481e0238593f85cc182b798fe3b77648c.tar.gz cpython-3d58b78481e0238593f85cc182b798fe3b77648c.tar.bz2 |
bpo-37558: Shared memory tests are failing due to double slashes (GH-14703)
With the addition of shared memory into Python 3.8, we now have three tests failing on Solaris, namely `test_multiprocessing_fork`, `test_multiprocessing_forkserver` and `test_multiprocessing_spawn`. The reason seems to be incorrect name handling which results in two slashes being prepended.
https://bugs.python.org/issue37558
(cherry picked from commit 4737265622251756a9480ab84af2442b6b986850)
Co-authored-by: Jakub KulĂk <Kulikjak@gmail.com>
-rw-r--r-- | Lib/test/_test_multiprocessing.py | 2 | ||||
-rw-r--r-- | Misc/NEWS.d/next/Tests/2019-07-11-10-33-56.bpo-37558.SKHRsL.rst | 1 |
2 files changed, 2 insertions, 1 deletions
diff --git a/Lib/test/_test_multiprocessing.py b/Lib/test/_test_multiprocessing.py index 9a39f38..2fe0def 100644 --- a/Lib/test/_test_multiprocessing.py +++ b/Lib/test/_test_multiprocessing.py @@ -3990,7 +3990,7 @@ class _TestSharedMemory(BaseTestCase): # Create a shared_memory segment, and send the segment name sm = shared_memory.SharedMemory(create=True, size=10) - sys.stdout.write(sm._name + '\\n') + sys.stdout.write(sm.name + '\\n') sys.stdout.flush() time.sleep(100) ''' diff --git a/Misc/NEWS.d/next/Tests/2019-07-11-10-33-56.bpo-37558.SKHRsL.rst b/Misc/NEWS.d/next/Tests/2019-07-11-10-33-56.bpo-37558.SKHRsL.rst new file mode 100644 index 0000000..9f393d7 --- /dev/null +++ b/Misc/NEWS.d/next/Tests/2019-07-11-10-33-56.bpo-37558.SKHRsL.rst @@ -0,0 +1 @@ +Fix test_shared_memory_cleaned_after_process_termination name handling |