Repository navigation
Repair wp/6.3 branch Actions: Remove the unused flaky test report uploads and reporter - #85107
Conversation
|
Important Review skippedAuto reviews are disabled on base/target branches other than the default branch. Please check the settings in the CodeRabbit UI or the ⚙️ Run configuration
You can disable this status message by setting the Use the checkbox below for a quick retry:
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
|
The following accounts have interacted with this PR and/or linked issues. I will continue to update these lists as activity occurs. You can also manually ask me to refresh this list by adding the If you're merging code through a pull request on GitHub, copy and paste the following into the bottom of the merge commit message. To understand the WordPress project's expectations around crediting contributors, please review the Contributor Attribution page in the Core Handbook. |
d7b9f27 to
1cc776d
Compare
1cc776d to
7304192
Compare
Part of #82930.
What?
Removes the flaky test reporting pieces that nothing uses any more:
.github/workflows/end2end-test.yml: removes both "Archive flaky tests report" steps (the Puppeteer and Playwright jobs).test/e2e/playwright.config.ts: drops./config/flaky-tests-reporter.tsfrom the CI reporters, leavinggithub, and deletestest/e2e/config/flaky-tests-reporter.ts.docs/contributors/code/testing-overview.md: no longer says flaky tests are reported to GitHub issues. The retry sentence stays: CI still retries failed tests twice.Why?
#83700 removed the
report-to-issuesjob, the only thing that read theflaky-tests-reportartifact and filed[Type] Flaky Testissues. The pieces that produce that artifact stayed, so every e2e run in which a test passes on retry still writesflaky-tests/*.jsonand uploads it, and nothing reads it.How?
The changes sit at the top of the stack so no other PR needs rebasing. No package changes. Left in place:
packages/e2e-tests/config/flaky-tests-reporter.js), its entry inpackages/e2e-tests/jest.config.jsand the comment about it insetup-test-framework.js. They're part of the published@wordpress/e2e-testspackage. Without the upload step, its files stay on the runner.packages/report-flaky-tests. Nothing runs the action any more, but removing the package changespackage.json,tsconfig.jsonandpackage-lock.json.Use of AI Tools
This PR was created by Claude Code under my supervision. All code should be treated as AI-produced and not yet reviewed by a human until this PR is marked Ready for Review.
🤖 Generated with Claude Code