-
Notifications
You must be signed in to change notification settings - Fork 1.6k
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
DockerLatentWorker: Handle not found exception when stopping #5308
Conversation
This pull request has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
I'll look into this in few weeks. |
If container is not found, log it.
Updated to catch the exception that's actually causing the problems. |
Codecov Report
@@ Coverage Diff @@
## master #5308 +/- ##
==========================================
- Coverage 91.82% 91.66% -0.17%
==========================================
Files 340 340
Lines 36371 36375 +4
==========================================
- Hits 33398 33342 -56
- Misses 2973 3033 +60
Continue to review full report at Codecov.
|
@cmouse Sorry for missing this PR. It looks good to me in principle. Could we add tests to cover this new behaviour? There's already a number of tests in |
Fixed in #8303. |
Contributor Checklist:
master/buildbot/newsfragments
directory (and read theREADME.txt
in that directory)If there is e.g. connectivity problem to the docker host, ensure we handle exceptions when stopping worker, otherwise the substantiation gets stuck on preparing worker.