Repository navigation
Repair wp/7.0 branch Actions: Remove the unused flaky test report uploads and reporter - #85114
Open
desrosj wants to merge 2 commits into
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 |
|
Size Change: 0 B Total Size: 7.61 MB ℹ️ View Unchanged
|
desrosj
marked this pull request as ready for review
October 19, 2026 17:03
|
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. |
desrosj
force-pushed
the
fix-actions-7.0/remove-flaky-test-report-leftovers
branch
from
October 19, 2026 17:04
01af526 to
9a9b2f0
Compare
desrosj
removed this pull request from stack #84468
October 21, 2026 18:35
desrosj
added this pull request to stack #85325
October 21, 2026 18:35
ramonjd
approved these changes
Oct 23, 2026
desrosj
force-pushed
the
fix-actions-7.0/remove-flaky-test-report-leftovers
branch
from
October 23, 2026 17:27
9a9b2f0 to
9acc931
Compare
This branch has not been deployed
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 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.
Part of #82782.
What?
Removes the flaky test reporting pieces that nothing uses any more:
.github/workflows/end2end-test.yml: removes the "Archive flaky tests report" step, and the "Merge flaky tests reports" step inmerge-artifacts(the job stays: it also merges the failure artifacts).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?
#82803 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/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