The clang_TSAN job from compiler_sanitizers.yml appears to use a container where all the Python packages are pre-installed. I don't know how and when this container is updated, so I'm not sure what is in there. Apparently it gets the newly released click 8.3.0, but it does not have the even newer spin 0.15. I could attempt to hack compiler_sanitizers.yml to upgrade spin before it is used to build numpy (probably right after pytest-xdist is removed), but I don't know if that is the "correct" solution for this job.

Edit: Let's give it a shot...

@ngoldbaum I see that you have opened other issues at https://github.com/nascheme/cpython_sanity/pkgs/container/numpy-tsan, seems we need another.

Edit: Let's give it a shot...

We can ignore/disable it for a while.

We can ignore/disable it for a while.

Go ahead and disable it, I’ll reenable it later this week with a fix.

Looks like @WarrenWeckesser fix works.

Yeah that works. The other thing that might be more sustainable is to use the cpython_tsan image and then install numpy’s build nd test dependencies from the requirements file like we do everywhere else. The only difference that numpy_tsan has is that it includes a numpy build and I think whoever added this used that to bootstrap the numpy build environment, but that leads to issues like this.

Let's get this in to fix the CI failures, we can tweak it later. Thanks Warren.