Skip to content

Unflake router events deploy test#91589

Merged
unstubbable merged 1 commit into
canaryfrom
hl/unflake-router-events-test
Mar 18, 2026
Merged

Unflake router events deploy test#91589
unstubbable merged 1 commit into
canaryfrom
hl/unflake-router-events-test

Conversation

@unstubbable
Copy link
Copy Markdown
Contributor

Flakiness metrics

After upgrading Playwright in #91250 (which brought some performance improvements), some tests are now exposed to be missing retries around assertions. test/e2e/basepath/router-events.test.ts is one of those tests, and this PR adds a retry around the event log assertion. We're also replacing the deprecated check utility with retry when waiting for the router to be ready.

[Flakiness metrics](https://app.datadoghq.com/ci/test/runs?query=test_level%3Atest%20%40git.repository.id%3A%22github.com%2Fvercel%2Fnext.js%22%20%40test.status%3A%22fail%22%20%40test.name%3A%22basePath%20should%20use%20urls%20with%20basepath%20in%20router%20events%20for%20hash%20changes%22&agg_m=count&agg_m_source=base&agg_t=count&currentTab=overview&eventStack=&fromUser=false&index=citest&start=1773244604685&end=1773849404685&paused=false)

After upgrading Playwright in #91250 (which brought some performance
improvements), some tests are now exposed to be missing retries around
assertions. `test/e2e/basepath/router-events.test.ts` is one of those
tests, and this PR adds a `retry` around the event log assertion. We're
also replacing the deprecated `check` utility with `retry` when waiting
for the router to be ready.
@nextjs-bot nextjs-bot added created-by: Next.js team PRs by the Next.js team. tests labels Mar 18, 2026
@unstubbable unstubbable enabled auto-merge (squash) March 18, 2026 16:11
@nextjs-bot
Copy link
Copy Markdown
Contributor

nextjs-bot commented Mar 18, 2026

Tests Passed

@unstubbable unstubbable merged commit 649d302 into canary Mar 18, 2026
280 of 283 checks passed
@unstubbable unstubbable deleted the hl/unflake-router-events-test branch March 18, 2026 16:34
@github-actions github-actions Bot added the locked label Apr 2, 2026
@github-actions github-actions Bot locked as resolved and limited conversation to collaborators Apr 2, 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.

3 participants