Repository navigation
Repair wp/6.8 branch Actions: Remove the broken flaky-test-to-GitHub-issues reporting job - #82889
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. |
4f0d6a7 to
197ad91
Compare
|
Size Change: 0 B Total Size: 1.85 MB ℹ️ View Unchanged
|
197ad91 to
5a92eb6
Compare
5a92eb6 to
10e80e8
Compare
10e80e8 to
b64c639
Compare
b64c639 to
1aaf7e0
Compare
1aaf7e0 to
d4836b2
Compare
Part of #82786.
What?
Removes the
report-to-issuesjob fromend2end-test.yml(and the now-unusedhas-flaky-test-reportoutput onmerge-artifactsthat fed it).Why?
This job checks out live
trunk— not this branch — before building and running./packages/report-flaky-tests, and has been failing outright withMissing script: "build:packages". Trunk retired that npm script when it migrated this action to run directly from TypeScript source via Node 24's native type stripping, avoiding a build step entirely (WordPress/gutenberg#81218).Because the job always tracks trunk's current state rather than a fixed target, this isn't a one-time regression to patch — it will keep breaking as trunk's build tooling continues to evolve, on every frozen branch that still has this job shape.
Retrofitting trunk's rewritten action was considered. It's technically feasible (the package is a self-contained leaf with no other consumers in the repo), but was rejected for this frozen, security-maintenance-only branch: trunk's rewrite is also a real product-policy change — flaky tests are now only commented on the PR, never filed as GitHub issues — which is more than a CI repair. Removing the job entirely only drops an automated notification; it doesn't affect any actual test-pass/fail signal, and the failure was easy to miss since the job only ever ran when
merge-artifacts.outputs.has-flaky-test-report == 'true'.packages/report-flaky-testsitself is left in place — it's now unused by any workflow on this branch, but removing the package is a separate, optional cleanup beyond this job fix.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.