-
-
Notifications
You must be signed in to change notification settings - Fork 461
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
test_concurrent_cwt
failure on macOS arm64 with free-threaded CPython
#758
Comments
Some of the NumPy wheels at https://anaconda.org/scientific-python-nightly-wheels/numpy/files are 11 days old, which is due to gh-26810. So if the fix landed already in numpy's |
I'm able to reproduce random failures and seg faults on this test using the wheel. I think rebuilding it will make this test more stable. That said, I do see a failure running a different test in the same file on the latest numpy
No idea why this fails randomly (a few percent of the time on my M3 Mac) in this way. |
Thanks for checking @ngoldbaum. That second failure looks like a problem in either CPython or Cython:
I can't find any existing bug report for this; |
I had a chat with @ambv over discord and he managed to find the upstream problem: python/cpython#121368. Closing in favor of that since this is unrelated to pywavelets. |
Except I don't have triage rights in this repo, so maybe @rgommers can do that. |
That's great, thanks @ngoldbaum and @ambv! |
We have a set of concurrent tests that use
concurrent.futures.ThreadPoolExecutor
. It has never failed before AFAIK; the tests also passed a number of times already with the new Linux free-threaded CI. It just now failed for the first time in the macOS arm64 free-threaded wheel build job (from the CI log):That looks like a missing lock around a cache in NumPy, which is probably already fixed by one of @ngoldbaum's PRs.
The text was updated successfully, but these errors were encountered: