Skip to content

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

Merged
merged 1 commit into from
Oct 6, 2021

Conversation

QuLogic
Copy link
Member

@QuLogic QuLogic commented Oct 5, 2021

PR Summary

It appears to no longer timeout on that system, and is breaking CI, which just switched to it.

PR Checklist

  • Has pytest style unit tests (and pytest passes).
  • Is Flake 8 compliant (run flake8 on changed files to check).
  • [n/a] New features are documented, with examples if plot related.
  • [n/a] Documentation is sphinx and numpydoc compliant (the docs should build without error).
  • [n/a] Conforms to Matplotlib style conventions (install flake8-docstrings and run flake8 --docstring-convention=all).
  • [n/a] New features have an entry in doc/users/next_whats_new/ (follow instructions in README.rst there).
  • [n/a] API changes documented in doc/api/next_api_changes/ (follow instructions in README.rst there).

@QuLogic QuLogic added this to the v3.5.0 milestone Oct 5, 2021
@QuLogic
Copy link
Member Author

QuLogic commented Oct 5, 2021

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.

@QuLogic
Copy link
Member Author

QuLogic commented Oct 5, 2021

So the CI information says it's macOS 11.6, but platform.mac_ver() says '10.16'.

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/
@QuLogic
Copy link
Member Author

QuLogic commented Oct 6, 2021

OK, apparently, macOS Big Sur reports both 10.16 and 11, depending on how Python might have been compiled.

@QuLogic
Copy link
Member Author

QuLogic commented Oct 6, 2021

My fork is apparently still on macOS 10.15 and passed, while this repo used macOS 11, so this is working for both.

Copy link
Contributor

@greglucas greglucas left a 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.

@jklymak jklymak merged commit 35f4778 into matplotlib:master Oct 6, 2021
meeseeksmachine pushed a commit to meeseeksmachine/matplotlib that referenced this pull request Oct 6, 2021
@QuLogic QuLogic deleted the fix-mac-ci branch October 6, 2021 07:58
timhoffm added a commit that referenced this pull request Oct 6, 2021
…288-on-v3.5.x

Backport PR #21288 on branch v3.5.x (Allow macosx thread safety test on macOS11)
tacaswell pushed a commit to tacaswell/matplotlib that referenced this pull request Oct 12, 2021
Allow macosx thread safety test on macOS11
tacaswell pushed a commit that referenced this pull request Oct 20, 2021
Allow macosx thread safety test on macOS11
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants