Fix e2e tests on macOS by replacing multiprocessing with threading #930
+25
−12
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
E2E tests segfault on macOS due to
multiprocessing.set_start_method('fork'). The fork start method is unsafe on macOS where system libraries may spawn threads, causing subprocess crashes.Changes
tests/e2e/conftest.py
multiprocessing.Processwiththreading.Timerfor browser timeout mechanismmultiprocessing.set_start_method('fork')callTEST_RUNNERconfig (Django-specific, not applicable to Flask)tests/conftest.py
TEST_RUNNERconfigImplementation
Threading is appropriate here—the timeout is a safety mechanism to quit hung browsers, not CPU-bound work requiring process isolation. No pickling required, no platform-specific start method issues.
Original prompt
✨ Let Copilot coding agent set things up for you — coding agent works faster and does higher quality work when set up for your repo.