Describe the bug
I don't understand why, but when running py.test eqcorrscan.tests.correlate_test.py::TestStreamCorrelateFunctions the first test (or any single test selected) runs fine, but following tests raise warnings from the C code about more threads selected than available - it appears that following the first test, omp_get_max_threads() returns 1.
To Reproduce
py.test eqcorrscan.tests.correlate_test.py::TestStreamCorrelateFunctions
Expected behavior
Python testing should not alter the behaviour of omp_get_max_threads...
Desktop (please complete the following information):
- Operating System: Manjaro (rolling, Gnome build 43.4)
- Python version: 3.9.12
- EQcorrscan version: 0.4.4
Additional context
This isn't something that happened after re-enabling outer core threading and is reproducible on the current master.
Describe the bug
I don't understand why, but when running
py.test eqcorrscan.tests.correlate_test.py::TestStreamCorrelateFunctionsthe first test (or any single test selected) runs fine, but following tests raise warnings from the C code about more threads selected than available - it appears that following the first test, omp_get_max_threads() returns 1.To Reproduce
Expected behavior
Python testing should not alter the behaviour of omp_get_max_threads...
Desktop (please complete the following information):
Additional context
This isn't something that happened after re-enabling outer core threading and is reproducible on the current master.