-
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
fix: distinguish docker build errors from streaming errors #6910
fix: distinguish docker build errors from streaming errors #6910
Conversation
Codecov Report
@@ Coverage Diff @@
## main #6910 +/- ##
==========================================
- Coverage 70.48% 68.84% -1.65%
==========================================
Files 515 551 +36
Lines 23150 25299 +2149
==========================================
+ Hits 16317 17416 +1099
- Misses 5776 6708 +932
- Partials 1057 1175 +118
Continue to review full report at Codecov.
|
What's odd here is that this error can appear long after the output started. Maybe |
Co-authored-by: Brian de Alwis <bdealwis@google.com>
Not sure, why |
I had it blocked pending the additional message. |
In trying to reproduce #6126, I noticed that docker build errors are oddly prefixed with "
unable to stream build output:
".It turns out that the Docker code for parsing and interpreting the JSON message stream from the Docker daemon parses build failures as a
JSONError
object, which behaves like anerror
. This PR changes our error-handling code to return such errors directly.