-
Notifications
You must be signed in to change notification settings - Fork 205
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 the timeout to consider workers offline configurable #3389
Conversation
7430378
to
7d35dd2
Compare
Codecov Report
@@ Coverage Diff @@
## master #3389 +/- ##
==========================================
+ Coverage 91.68% 91.71% +0.02%
==========================================
Files 216 216
Lines 13253 13264 +11
==========================================
+ Hits 12151 12165 +14
+ Misses 1102 1099 -3
Continue to review full report at Codecov.
|
* This should avoid jobs being stuck in the assigned state too long when a worker disconnects unexpectedly. * See https://progress.opensuse.org/issues/69784#note-11
* Avoid marking assigned jobs as incomplete and set them instead back to scheduled * Consider all jobs assigned to a worker (with directly chained dependencies multiple jobs might be assigned to a worker) * See https://progress.opensuse.org/issues/69784#note-11
7d35dd2
to
585a0a3
Compare
so similar to what @kalikiana was working on here we should also ensure that we have a time limit within 33-developer-mode.t which is less than 10m. I prepared #3393 for this. |
And, too, addressing the potential cause for it: #3394 |
@kalikiana excellent :) |
See https://progress.opensuse.org/issues/69784#note-12