-
-
Notifications
You must be signed in to change notification settings - Fork 7.9k
Allow macosx thread safety test on macOS11 #21288
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
Conversation
The CI setup definitely shows that it's the macOS 11 builders that fail, but I guess what I'm checking is not sufficient to differentiate. |
So the CI information says it's macOS 11.6, but |
It appears to no longer timeout on that system, and is breaking CI, which just switched to it. Note, macOS plays games with the version number it reports depending on how Python was compiled: https://eclecticlight.co/2020/08/13/macos-version-numbering-isnt-so-simple/
OK, apparently, macOS Big Sur reports both 10.16 and 11, depending on how Python might have been compiled. |
My fork is apparently still on macOS 10.15 and passed, while this repo used macOS 11, so this is working for both. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Interesting that your fork got run on a different OS version.
…288-on-v3.5.x Backport PR #21288 on branch v3.5.x (Allow macosx thread safety test on macOS11)
Allow macosx thread safety test on macOS11
Allow macosx thread safety test on macOS11
PR Summary
It appears to no longer timeout on that system, and is breaking CI, which just switched to it.
PR Checklist
pytest
passes).flake8
on changed files to check).flake8-docstrings
and runflake8 --docstring-convention=all
).doc/users/next_whats_new/
(follow instructions in README.rst there).doc/api/next_api_changes/
(follow instructions in README.rst there).