Skip to content
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

CI: Make macOS Intel required to succeed #110362

Merged
merged 3 commits into from
Nov 3, 2023

Conversation

hugovk
Copy link
Member

@hugovk hugovk commented Oct 4, 2023

Intel-based macOS aka build_macos aka x86_64-apple-darwin is Tier 1 in PEP 11, which means:

  • CI failures block releases.
  • Changes which would break the main branch are not allowed to be merged; any breakage should be fixed or reverted immediately.
  • All core developers are responsible to keep main, and thus these platforms, working.
  • Failures on these platforms block a release.

Let's remove it from the "allowed to fail" list so that it is "required to succeed".

(Windows x86 (32-bit) aka build_win32 aka x86_64-pc-windows-msvc is also Tier 1, but I'm not making it required in this PR because some tests are still flaky.)


Also remove EOL Python 3.7 from the list of branches. (Or we probably only need bugfix and newer, 3.11+.)

@vstinner
Copy link
Member

vstinner commented Oct 5, 2023

Be careful: there is known bug on macOS: #110083

@vstinner
Copy link
Member

vstinner commented Oct 5, 2023

In terms of performance, the GHA macOS now seem to have good performance, between Linux and Windows:

  • Ubuntu: 13 min (tests: Total duration: 11 min 11 sec)
  • macOS: 17 min (tests: Total duration: 13 min 28 sec)
  • Windows x64: 27 min (tests: Total duration: 22 min 59 sec)

@hugovk
Copy link
Member Author

hugovk commented Oct 5, 2023

Be careful: there is known bug on macOS: #110083

Shall we wait until it's fixed?

@vstinner
Copy link
Member

vstinner commented Oct 5, 2023

Shall we wait until it's fixed?

I didn't check the failure rate. So far, the job was non-voting (didn't block a PR if it failed). I'm tracking too many tests: https://github.com/python/cpython/issues/vstinner :-)

@vstinner
Copy link
Member

vstinner commented Oct 5, 2023

cc @sobolevn

@ambv ambv merged commit 5add7a6 into python:main Nov 3, 2023
28 checks passed
@miss-islington-app
Copy link

Thanks @hugovk for the PR, and @ambv for merging it 🌮🎉.. I'm working now to backport this PR to: 3.11, 3.12.
🐍🍒⛏🤖

@miss-islington-app
Copy link

Sorry, @hugovk and @ambv, I could not cleanly backport this to 3.12 due to a conflict.
Please backport using cherry_picker on command line.

cherry_picker 5add7a6724cbff6c9f0597f0257b64c4f0978c14 3.12

@miss-islington-app
Copy link

Sorry, @hugovk and @ambv, I could not cleanly backport this to 3.11 due to a conflict.
Please backport using cherry_picker on command line.

cherry_picker 5add7a6724cbff6c9f0597f0257b64c4f0978c14 3.11

@hugovk hugovk deleted the ci-macos-required-to-succeed branch November 3, 2023 15:14
aisk pushed a commit to aisk/cpython that referenced this pull request Feb 11, 2024
Glyphack pushed a commit to Glyphack/cpython that referenced this pull request Sep 2, 2024
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