build: remove macOS nightly release tests #29005
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
codebytere
approved these changes
May 5, 2021
VerteDinde
approved these changes
May 5, 2021
jkleinsc
approved these changes
May 5, 2021
|
Merging as CI failures are unrelated to PR change. |
|
No Release Notes |
5 tasks
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
These have been failing due to out of disk space for months now, they provide no signal (we don't even get alerts for them in #bot-nightly-ci) and they consume our valuable and limited macOS resources early in the morning when they could be going to actual nightly/beta/stable release jobs.
This is also part of a wider plan I have to greatly simplify our CI config with the eventual goal of using CircleCI setup workflows which will allow us to do substantially cooler and cleverer things with regards to how we run CI.
It's also worth noting that the
chromium-upgrade-branchespattern hasn't matched chromium upgrades for a long time, it's beenroller/chromium/*since we brought roller bot to lifeNotes: no-notes