summaryrefslogtreecommitdiff
path: root/numpy/array_api/_array_object.py
diff options
context:
space:
mode:
authorJyn Spring 琴春 <me@vx.st>2022-09-07 14:35:06 +0700
committerGitHub <noreply@github.com>2022-09-07 09:35:06 +0200
commit5e9ec76a20062ec8bb7ee0c936be28c63837b6dd (patch)
treee6d78a8215e2f627d568548d6e34e22e073a0481 /numpy/array_api/_array_object.py
parent7a17d01977e5e6a9b7ef8f4c435235e711bc97be (diff)
downloadnumpy-5e9ec76a20062ec8bb7ee0c936be28c63837b6dd.tar.gz
TST,BUG: Us context from spawn to fork in (#22204)
Since Python 3.8, the default start method for multiprocessing has been changed from fork to spawn on macOS The default start method is still fork on other Unix platforms[1], causing inconsistency on memory sharing model It will cause a memory-sharing problem for the test test_large_zip on macOS as the memory sharing model between spawn and fork is different The fix Change the start method for this test back to fork under this testcase context In this test case context, the bug that caused default start method changed to spawn for macOS will not be triggered It is context limited, so this change will not affect default start method other than test_large_zip All platforms have the same memory sharing model now After the change, test_large_zip is passed on macOS https://docs.python.org/3/library/multiprocessing.html#contexts-and-start-methods Closes gh-22203
Diffstat (limited to 'numpy/array_api/_array_object.py')
0 files changed, 0 insertions, 0 deletions