You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Seems to be since #7429 went in - in the build controller, we now see things like:
{"level":"info","msg":"storing logs for activity jenkins-x-jx-master-970 into storage at jenkins-x/logs/jenkins-x/jx/master/970.log","time":"2020-07-20T12:51:19Z"}
{"level":"error","msg":"failed to store logs for activity jenkins-x-jx-master-970 into storage at jenkins-x/logs/jenkins-x/jx/master/970.log: failed to write key jenkins-x/logs/jenkins-x/jx/master/970.log in bucket gs://logs-oss-weasel-e5201f35d164: short write","time":"2020-07-20T12:51:24Z"}
{"level":"warning","msg":"failed to write key jenkins-x/logs/jenkins-x/jx/master/970.log in bucket gs://logs-oss-weasel-e5201f35d164: short write","time":"2020-07-20T12:51:24Z"}
Not sure what went wrong there, but something's definitely awry.
The text was updated successfully, but these errors were encountered:
For some reason, `io.Copy` was resulting in a "short write" error in
the build controller, and the best suspicion I've got at this point is
that it's a problem with the bucket writer closing early or something
along those lines. So let's instead go back to earlier behavior and
read the reader contents and write that directly rather than relying
on `io.Copy`.
fixesjenkins-x#7461 (hopefully!)
Signed-off-by: Andrew Bayer <andrew.bayer@gmail.com>
For some reason, `io.Copy` was resulting in a "short write" error in
the build controller, and the best suspicion I've got at this point is
that it's a problem with the bucket writer closing early or something
along those lines. So let's instead go back to earlier behavior and
read the reader contents and write that directly rather than relying
on `io.Copy`.
fixes#7461 (hopefully!)
Signed-off-by: Andrew Bayer <andrew.bayer@gmail.com>
Seems to be since #7429 went in - in the build controller, we now see things like:
Not sure what went wrong there, but something's definitely awry.
The text was updated successfully, but these errors were encountered: