Skip to content

Python 3.8 + Multiprocessing #3209

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom
Open
effigies opened this issue Apr 20, 2020 · 1 comment
Open

Python 3.8 + Multiprocessing #3209

effigies opened this issue Apr 20, 2020 · 1 comment

Comments

@effigies
Copy link
Member

In #3154, several tests had to be marked skip, xfail or timeout to deal with some new quirk of multiprocessing. It seems likely to be a combination of the following:

  • Python 3.8 multiprocessing module
  • pytest subprocesses (xdist)
  • Nipype configurations for setting up concurrent.futures and multiprocessing in the MultiProc/LegacyMultiProc plugins
@effigies
Copy link
Member Author

effigies commented Apr 26, 2020 •
edited
Loading

Also, nipype/pipeline/plugins/tests/test_callback.py::test_callback_exception[False-LegacyMultiProc] times out in https://travis-ci.org/github/nipy/nipype/jobs/679493619.

Should mark with 60s timeout or other sensible value.

Edit: Made the mistake of restarting, and Travis doesn't register a new job ID for reruns... it may not show an error

@mattcieslak mattcieslak mentioned this issue Jan 11, 2024
Closed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@effigies