-
Notifications
You must be signed in to change notification settings - Fork 206
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Make it less likely for jobs incompleting with Cache … queue … full
#5500
Conversation
b0f1daa
to
34a0b55
Compare
34a0b55
to
9812106
Compare
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## master #5500 +/- ##
=======================================
Coverage 98.38% 98.38%
=======================================
Files 391 391
Lines 37910 37926 +16
=======================================
+ Hits 37298 37314 +16
Misses 612 612 ☔ View full report in Codecov by Sentry. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
There might be more points. Just had one question for a start. Will look into more later.
* Introduce a hard-limit for inactive Minion jobs * Make the hard-limit slightly higher than the normal limit * Enforce only the hard-limit on openQA job setup; so when the normal Minion queue limit was reached after a job had already been picked-up it can still continue to create Minion jobs instead of ending up as incomplete * See https://progress.opensuse.org/issues/128276
9812106
to
d27d56d
Compare
commit 90519fe Merge: 8fc02ca d27d56d Author: mergify[bot] <37929162+mergify[bot]@users.noreply.github.com> AuthorDate: Thu Mar 7 14:45:11 2024 +0000 Commit: GitHub <[email protected]> CommitDate: Thu Mar 7 14:45:11 2024 +0000 Merge pull request os-autoinst#5500 from Martchus/cache-queue-hard-limit Make it less likely for jobs incompleting with `Cache … queue … full`
Still a draft because tests are missing.