Repository navigation
Repair wp/6.6 branch Actions: Remove the broken flaky-test issue reporting job - #82921
Open
desrosj wants to merge 1 commit 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 |
desrosj
added this pull request to stack #82927
September 15, 2026 00:46
desrosj
marked this pull request as ready for review
September 15, 2026 01:18
|
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
removed this pull request from stack #82927
September 21, 2026 15:45
desrosj
added this pull request to stack #83282
September 21, 2026 15:45
desrosj
removed this pull request from stack #83282
September 21, 2026 18:43
desrosj
changed the base branch from
fix-actions-6.6/fix-wp-env-debian-buster
to
wp/6.6
September 21, 2026 18:43
desrosj
force-pushed
the
fix-actions-6.6/disable-flaky-test-issue-reporting
branch
from
September 21, 2026 18:53
6fec339 to
a259cd7
Compare
desrosj
changed the base branch from
wp/6.6
to
fix-actions-6.6/fix-wp-env-debian-buster
September 21, 2026 18:55
desrosj
added this pull request to stack #83289
September 21, 2026 18:55
|
Size Change: 0 B Total Size: 1.73 MB ℹ️ View Unchanged
|
desrosj
removed this pull request from stack #83289
September 22, 2026 17:08
desrosj
changed the base branch from
fix-actions-6.6/fix-wp-env-debian-buster
to
wp/6.6
September 22, 2026 17:08
desrosj
force-pushed
the
fix-actions-6.6/disable-flaky-test-issue-reporting
branch
from
September 22, 2026 17:09
a259cd7 to
17ea30b
Compare
desrosj
changed the base branch from
wp/6.6
to
fix-actions-6.6/simplify-pr-label-enforcement
September 22, 2026 17:11
desrosj
added this pull request to stack #83396
September 22, 2026 17:11
desrosj
removed this pull request from stack #83396
September 22, 2026 22:36
desrosj
changed the base branch from
fix-actions-6.6/simplify-pr-label-enforcement
to
wp/6.6
September 22, 2026 22:53
desrosj
force-pushed
the
fix-actions-6.6/disable-flaky-test-issue-reporting
branch
from
September 22, 2026 23:31
17ea30b to
f2984a3
Compare
desrosj
changed the base branch from
wp/6.6
to
fix-actions-6.6/simplify-pr-label-enforcement
September 22, 2026 23:33
desrosj
added this pull request to stack #83415
September 22, 2026 23:33
desrosj
removed this pull request from stack #83415
September 28, 2026 15:25
desrosj
added this pull request to stack #83628
September 28, 2026 15:27
desrosj
removed this pull request from stack #83628
September 28, 2026 17:57
desrosj
added this pull request to stack #83644
September 28, 2026 17:59
desrosj
force-pushed
the
fix-actions-6.6/disable-flaky-test-issue-reporting
branch
from
October 7, 2026 14:18
f2984a3 to
a4a0c58
Compare
desrosj
removed this pull request from stack #83644
October 7, 2026 18:12
desrosj
changed the base branch from
fix-actions-6.6/simplify-pr-label-enforcement
to
wp/6.6
October 7, 2026 18:12
desrosj
force-pushed
the
fix-actions-6.6/disable-flaky-test-issue-reporting
branch
from
October 7, 2026 18:15
a4a0c58 to
7c68b8f
Compare
desrosj
changed the base branch from
wp/6.6
to
fix-actions-6.6/simplify-pr-label-enforcement
October 7, 2026 18:16
desrosj
added this pull request to stack #84184
October 7, 2026 18:17
desrosj
removed this pull request from stack #84184
October 8, 2026 18:41
desrosj
changed the base branch from
fix-actions-6.6/simplify-pr-label-enforcement
to
wp/6.6
October 8, 2026 18:41
desrosj
changed the base branch from
wp/6.6
to
fix-actions-6.6/simplify-pr-label-enforcement
October 8, 2026 18:45
desrosj
added this pull request to stack #84339
October 8, 2026 18:46
desrosj
removed this pull request from stack #84339
October 8, 2026 21:28
desrosj
changed the base branch from
fix-actions-6.6/simplify-pr-label-enforcement
to
wp/6.6
October 8, 2026 21:28
desrosj
force-pushed
the
fix-actions-6.6/disable-flaky-test-issue-reporting
branch
from
October 8, 2026 21:30
7c68b8f to
8850796
Compare
desrosj
changed the base branch from
wp/6.6
to
fix-actions-6.6/fix-workflow-branch-filters
October 8, 2026 21:31
desrosj
added this pull request to stack #84351
October 8, 2026 21:32
desrosj
removed this pull request from stack #84351
October 9, 2026 23:44
desrosj
changed the base branch from
fix-actions-6.6/fix-workflow-branch-filters
to
wp/6.6
October 9, 2026 23:45
desrosj
force-pushed
the
fix-actions-6.6/disable-flaky-test-issue-reporting
branch
from
October 9, 2026 23:46
8850796 to
eb0caae
Compare
desrosj
changed the base branch from
wp/6.6
to
fix-actions-6.6/fix-workflow-branch-filters
October 9, 2026 23:48
desrosj
added this pull request to stack #84476
October 9, 2026 23:49
desrosj
changed the title
wp/6.6 branch Actions: Remove the broken flaky-test-to-GitHub-issues reporting jobwp/6.6 branch Actions: Remove the broken flaky-test issue reporting job
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
1 participant
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 #82784.
What?
Removes
end2end-test.yml'sreport-to-issuesjob, which posts flaky end-to-end test summaries as GitHub issues, along with thehas-flaky-test-reportoutput onmerge-artifactsthat fed it (its only consumer).Why?
report-to-issuesdoesactions/checkout … ref: trunkbefore building and running./packages/report-flaky-tests— so it never runs this branch's own frozen copy of the action, it runs whatever is on live current trunk at the time the job happens to execute. Trunk has since retired thenpm run build:packagesscript this job's "Npm build" step calls, as part of migratingreport-flaky-teststo run directly from TypeScript source via Node 24's native type-stripping (WordPress/gutenberg#81218, "Flaky tests: Report as a PR comment only, stop creating issues").Reproducing the job's own build command against trunk's current
package.jsonconfirms the exact failure:This branch's most recent
end2end-test.ymlrun (fix-actions-6.6/fix-wp-env-debian-buster, run 33230071941) happened to have this job report asskippedrather thanfailure, because the upstreame2e-playwrightjobs failed outright and no flaky-tests-report artifact was ever produced formerge-artifactsto hand off — but the underlying breakage is unconditional: any time the job's guard condition (needs.merge-artifacts.outputs.has-flaky-test-report == 'true') is met, it will fail with the error above, since it depends on a script that no longer exists on trunk.Because the job tracks a moving target (trunk) instead of this branch's own commit, it will keep breaking in step with trunk's tooling regardless of anything on this frozen, security-maintenance-only branch — this is a structural failure mode, not a one-time regression.
Retrofitting the job to match trunk's current implementation was considered and rejected: trunk's replacement is not just a CI fix but a product-policy change (flaky tests are now reported as PR comments instead of filed as GitHub issues), which is out of scope for a security-maintenance branch. Removing the job only drops an automated notification; it has no effect on actual test-correctness signal, since it never gated the build and only ever posted flaky-test summaries as GitHub issues.
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.