Repository navigation
[ci] Run flake detection and new deploy tests when merged and on backport branches - #97991
Merged
Merged
Conversation
Contributor
Tests PassedCommit: 290bf69 |
![vercel[bot]](https://avatars.githubusercontent.com/in/8329?s=60&v=4){kind=small}
This comment was marked as resolved.
This comment was marked as resolved.
Sorry, something went wrong.
eps1lon
force-pushed
the
sebbie/changed-tests-backport-branches
branch
from
August 27, 2026 18:55
4ebe506 to
f1f746d
Compare
eps1lon
force-pushed
the
sebbie/changed-tests-backport-branches
branch
from
August 27, 2026 18:57
f1f746d to
290bf69
Compare
eps1lon
marked this pull request as ready for review
August 27, 2026 19:20
unstubbable
approved these changes
Aug 28, 2026
unstubbable
approved these changes
Aug 28, 2026
eps1lon
enabled auto-merge (squash)
August 28, 2026 09:02
eps1lon
added a commit
that referenced
this pull request
Aug 28, 2026
… on backport branches (#97991) The previous detection mechanism special-cased `canary` which lead to large diffs when backport branches ran CI. We stop special casing `canary` reducing complexity and giving us another flake-detecting attempt when the change is merged. That way we can safely enable flake detection on backport branches without having to test large diffs when PRs are merged targetting backport branches. New backport branches will no longer have flake detecton and new deploy test runs disabled.
eps1lon
added a commit
that referenced
this pull request
Aug 28, 2026
… on backport branches (#97991) The previous detection mechanism special-cased `canary` which lead to large diffs when backport branches ran CI. We stop special casing `canary` reducing complexity and giving us another flake-detecting attempt when the change is merged. That way we can safely enable flake detection on backport branches without having to test large diffs when PRs are merged targetting backport branches. New backport branches will no longer have flake detecton and new deploy test runs disabled.
This file contains hidden or 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
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
2 participants
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.
The previous detection mechanism special-cased
canarywhich lead to large diffs when backport branches ran CI.We stop special casing
canaryreducing complexity and giving us another flake-detecting attempt when the change is merged.That way we can safely enable flake detection on backport branches without having to test large diffs when PRs are merged targetting backport branches. New backport branches will no longer have flake detecton and new deploy test runs disabled.