Hopefully we can make it so we can run tests that handle warnings under 3.14, now that the warnings module is thread-safe.
Someone needs to make sure that pytest's warning handling is itself thread-safe by trying to run e.g. the scipy tests or artificial tests that make heavy use of warnings to prove that things are indeed thread-safe on 3.14.
In that case, we can modify the logic that skips running tests that use thread-unsafe functionality in parallel to only skip tests that handle warnings on 3.13 and older.