Skip to content

[15.5.x][ci] Run flake detection and new deploy tests when merged and on backport branches - #98019

Merged
eps1lon merged 1 commit into
next-15-5from
sebbie/new-test-backport/15-5
Aug 28, 2026
Merged

eps1lon merged 1 commit into
next-15-5from
sebbie/new-test-backport/15-5

Conversation

@eps1lon

@eps1lon eps1lon commented Aug 28, 2026 •

Copy link
Copy Markdown
Member

Backports #97991

vercel[bot]

This comment was marked as resolved.

@eps1lon
eps1lon force-pushed the sebbie/new-test-backport/15-5 branch from caa9353 to 3792a52 Compare August 28, 2026 10:56
@github-actions

github-actions Bot commented Aug 28, 2026 •

Copy link
Copy Markdown
Contributor

Tests Passed

Commit: d9cc6bc

… 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
eps1lon force-pushed the sebbie/new-test-backport/15-5 branch from 3792a52 to d9cc6bc Compare August 28, 2026 11:08
@eps1lon
eps1lon marked this pull request as ready for review August 28, 2026 11:12
@eps1lon
eps1lon requested a review from unstubbable August 28, 2026 11:12

@unstubbable unstubbable left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks like this also backports #85619?

@eps1lon
eps1lon enabled auto-merge (squash) August 28, 2026 17:07
@eps1lon
eps1lon merged commit 1a80896 into next-15-5 Aug 28, 2026
404 of 411 checks passed
@eps1lon
eps1lon deleted the sebbie/new-test-backport/15-5 branch August 28, 2026 17:20
@github-actions github-actions Bot locked as resolved and limited conversation to collaborators Sep 12, 2026
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants