Drone 2.0 Builds failing, not presenting output

Hello,

We updated to drone 2.0 and are having issues with builds stopping on some steps, and locking the output for the entire stage. This wasn’t happening before the updated.

I would include more screenshots but discourse won’t let me

Clicking on a successful step within that stage shows an error message, and the same message is shown if you click on the failed step.

Looking at the network requests made from the UI, I can see that the response for the successful step includes the correct information, but it is not showing. The response for the errored step, however, is just null.

This is not limited to just one particular stage or step. I had a screenshot of it happening to another one here, but discourse won’t let me put it in.

Looking at the docker logs, there’s a few entries about not being able to tear down log streams. I’m not sure if it’s related.

{“error”:“stream: not found”,“level”:“warning”,“msg”:“manager: cannot teardown log stream”,“step.id”:589022,“step.name”:“archive”,“step.status”:“skipped”,“time”:“2021-05-27T02:05:04Z”}
{“error”:“stream: not found”,“level”:“warning”,“msg”:“manager: cannot teardown log stream”,“step.id”:589048,“step.name”:“archive”,“step.status”:“skipped”,“time”:“2021-05-27T02:05:30Z”}
{“error”:“stream: not found”,“level”:“warning”,“msg”:“manager: cannot teardown log stream”,“step.id”:589096,“step.name”:“tools”,“step.status”:“skipped”,“time”:“2021-05-27T02:05:40Z”}
{“error”:“stream: not found”,“level”:“warning”,“msg”:“manager: cannot teardown log stream”,“step.id”:589111,“step.name”:“tools”,“step.status”:“skipped”,“time”:“2021-05-27T02:05:40Z”}
{“error”:“stream: not found”,“level”:“warning”,“msg”:“manager: cannot teardown log stream”,“step.id”:589097,“step.name”:“static-analysis”,“step.status”:“skipped”,“time”:“2021-05-27T02:05:40Z”}
{“error”:“stream: not found”,“level”:“warning”,“msg”:“manager: cannot teardown log stream”,“step.id”:589112,“step.name”:“windows”,“step.status”:“skipped”,“time”:“2021-05-27T02:05:40Z”}
{“error”:“stream: not found”,“level”:“warning”,“msg”:“manager: cannot teardown log stream”,“step.id”:589098,“step.name”:“tests”,“step.status”:“skipped”,“time”:“2021-05-27T02:05:40Z”}
{“error”:“stream: not found”,“level”:“warning”,“msg”:“manager: cannot teardown log stream”,“step.id”:589113,“step.name”:“linux”,“step.status”:“skipped”,“time”:“2021-05-27T02:05:40Z”}
{“error”:“stream: not found”,“level”:“warning”,“msg”:“manager: cannot teardown log stream”,“step.id”:589099,“step.name”:“send-coverage”,“step.status”:“skipped”,“time”:“2021-05-27T02:05:40Z”}
{“error”:“stream: not found”,“level”:“warning”,“msg”:“manager: cannot teardown log stream”,“step.id”:589100,“step.name”:“archive”,“step.status”:“skipped”,“time”:“2021-05-27T02:05:40Z”}
{“error”:“stream: not found”,“level”:“warning”,“msg”:“manager: cannot teardown log stream”,“step.id”:589130,“step.name”:“tests”,“step.status”:“skipped”,“time”:“2021-05-27T02:05:48Z”}
{“error”:“stream: not found”,“level”:“warning”,“msg”:“manager: cannot teardown log stream”,“step.id”:589132,“step.name”:“send-coverage”,“step.status”:“skipped”,“time”:“2021-05-27T02:05:48Z”}
{“error”:“stream: not found”,“level”:“warning”,“msg”:“manager: cannot teardown log stream”,“step.id”:589134,“step.name”:“archive”,“step.status”:“skipped”,“time”:“2021-05-27T02:05:48Z”}

There seems to be 2/3 issues here.

The first is that the output view is being blocked by the error message.

The second is that random bits of the build are dying. (Seems to be after 3 seconds each time?)

The third is that there’s no useful error message.

Rolled back to 1.10.1

Looks like the issue was that we were requesting too much from docker.

It’s not that drone was randomly killing builds, but it wasn’t presenting the error message in a useful way, and concealing output that it shouldn’t be