Add monthly unit-test re-trigger flakiness report - #5481
Merged
Merged
Conversation
Scheduled workflow computing the monthly re-trigger rate of the Unit Tests workflow on main, upserted into a data file and README chart on the reports/unit-test-flakiness branch. A run counts as flaky when its final run_attempt >= 2 and it went green; still-failing re-runs are excluded. Upserting preserves months past GitHub's ~400-day run retention. No external storage or secrets.
johha
approved these changes
Sep 25, 2026
ari-wg-gitbot
added a commit
to cloudfoundry/capi-release
that referenced
this pull request
Sep 25, 2026
Changes in cloud_controller_ng:
- Add monthly unit-test re-trigger flakiness report
PR: cloudfoundry/cloud_controller_ng#5481
Author: Philipp Thun <philipp.thun@sap.com>
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
2 participants
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.
Scheduled workflow computing the monthly re-trigger rate of the Unit Tests workflow on main, upserted into a data file and README chart on the reports/unit-test-flakiness branch.
A run counts as flaky when its final run_attempt >= 2 and it went green; still-failing re-runs are excluded. Upserting preserves months past GitHub's ~400-day run retention. No external storage or secrets.
This change was developed with AI assistance; all code was reviewed and tested by me.
I have reviewed the contributing guide
I have viewed, signed, and submitted the Contributor License Agreement
I have made this pull request to the
mainbranchI have run all the unit tests using
bundle exec rakeI have run CF Acceptance Tests