BUG test_thread_bomb_mitigation resulted in crashed interpreter #1150
Description
While doing some changes relaed to Memory, I stumbled upon this weird one for test config Testing linux_py37_distributed: https://dev.azure.com/joblib/joblib/_build/results?buildId=1015&view=logs&jobId=9ab96c21-2bfa-5360-3f04-0ac557a9e9b9&j=9ab96c21-2bfa-5360-3f04-0ac557a9e9b9&t=9e7dbc11-35ad-5252-3da3-844606a02961
The end of the log is:
oblib/test/test_parallel.py::test_thread_bomb_mitigation[loky] [DEBUG:MainProcess:Thread-633] worker got sentinel -- exiting
[DEBUG:MainProcess:Thread-633] worker exiting after 2 tasks
[DEBUG:MainProcess:Thread-634] worker got sentinel -- exiting
[DEBUG:MainProcess:Thread-634] worker exiting after 1 tasks
XFAIL [ 96%]
joblib/test/test_parallel.py::test_thread_bomb_mitigation[threading] continuous_integration/run_tests.sh: line 25: 3387 Aborted (core dumped) pytest joblib -vl --timeout=60 --junitxml="${JUNITXML}"
##[error]Bash exited with code '134'.
Exit code 134 seems to not be very informative, seems to be SIGABRT.
Not sure if it happens often but let's keep track of this one if it repeats and investigate if needed.