ci: delay all-green check for six minutes and activate verbose mode#7329
Merged
ci: delay all-green check for six minutes and activate verbose mode#7329
Conversation
This should a) reduce github API rate limit usages and b) increase the overall successrate of the all-green job for long running processes as well as jobs that hit the API rate limit early on. Six minutes is choosen as our CI normally needs about twice as long overall and even if we optimize slow runs away, we likely will not drop below six minutes. The verbose mode allows to understand better why the job fails, which is currently partially difficult.
Contributor
Overall package sizeSelf size: 4.45 MB Dependency sizes| name | version | self size | total size | |------|---------|-----------|------------| | import-in-the-middle | 2.0.3 | 76.87 kB | 808.03 kB | | dc-polyfill | 0.1.10 | 26.73 kB | 26.73 kB |🤖 This report was automatically generated by heaviest-objects-in-the-universe |
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## master #7329 +/- ##
=======================================
Coverage 86.03% 86.03%
=======================================
Files 513 513
Lines 22219 22219
=======================================
Hits 19117 19117
Misses 3102 3102 Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
BenchmarksBenchmark execution time: 2026-01-25 10:54:36 Comparing candidate commit b71dd45 in PR branch Found 0 performance improvements and 0 performance regressions! Performance is the same for 230 metrics, 30 unstable metrics. |
watson
requested changes
Jan 25, 2026
Collaborator
watson
left a comment
watson
left a comment
There was a problem hiding this comment.
This would mean, that if a test is flaky and we'll have to re-run all-green after the flaky test has passed, we'd have to wait delay-minutes. For me unfortunately that's a blocker
Member
Author
|
@watson good point, I just pushed another commit to only use the delay on the first run. |
watson
approved these changes
Jan 25, 2026
dd-octo-sts bot
pushed a commit
that referenced
this pull request
Jan 27, 2026
…7329) This should a) reduce github API rate limit usages and b) increase the overall success rate of the all-green job for long running processes as well as jobs that hit the API rate limit early on. Six minutes is chosen as our CI normally needs about twice as long overall and even if we optimize slow runs away, we likely will not drop below six minutes. Re-running our CI will not have the delay. The verbose mode allows to understand better why the job fails, which is currently partially difficult.
Merged
BridgeAR
added a commit
that referenced
this pull request
Jan 30, 2026
…7329) This should a) reduce github API rate limit usages and b) increase the overall success rate of the all-green job for long running processes as well as jobs that hit the API rate limit early on. Six minutes is chosen as our CI normally needs about twice as long overall and even if we optimize slow runs away, we likely will not drop below six minutes. Re-running our CI will not have the delay. The verbose mode allows to understand better why the job fails, which is currently partially difficult.
BridgeAR
added a commit
that referenced
this pull request
Feb 22, 2026
…7329) This should a) reduce github API rate limit usages and b) increase the overall success rate of the all-green job for long running processes as well as jobs that hit the API rate limit early on. Six minutes is chosen as our CI normally needs about twice as long overall and even if we optimize slow runs away, we likely will not drop below six minutes. Re-running our CI will not have the delay. The verbose mode allows to understand better why the job fails, which is currently partially difficult.
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.
This should a) reduce github API rate limit usages and b) increase the overall successrate of the all-green job for long running processes as well as jobs that hit the API rate limit early on.
Six minutes is choosen as our CI normally needs about twice as long overall and even if we optimize slow runs away, we likely will not drop below six minutes.
The verbose mode allows to understand better why the job fails, which is currently partially difficult.