Last part of step logs not always shown

[bradrydzewski]

Please provide the version and image of the docker runner you are using. Have you confirmed both the runner and the Drone server are using the latest stable releases so that we are not triaging something that has already been fixed in a newer release?

@SimonVHB

This behaviour happens a lot, not only on failing steps, but always with these logs:

{"error":"stream: not found","level":"warning","msg":"manager: cannot teardown log stream","step.id":6753,"step.name":"linting check","step.status":"skipped","time":"2021-05-10T16:08:14Z"}
{"error":"stream: not found","level":"warning","msg":"manager: cannot teardown log stream","step.id":6754,"step.name":"formatting check","step.status":"skipped","time":"2021-05-10T16:08:14Z"}
{"error":"stream: not found","level":"warning","msg":"manager: cannot teardown log stream","step.id":6758,"step.name":"dead code check","step.status":"skipped","time":"2021-05-10T16:08:14Z"}
{"error":"stream: not found","level":"warning","msg":"manager: cannot teardown log stream","step.id":6750,"step.name":"Notify slack on failure","step.status":"skipped","time":"2021-05-10T16:11:24Z"}

What could be causing this?

These log entries are normal and are not indicative of a problem.

@SimonVHB

We are running drone on a single VM using the docker runner. We’ve noticed that a lot of the times the last part of the logs of a step aren’t shown.

I recommend enabling debug mode (Piping conversion extensions) and re-running the pipeline in debug mode. When running in debug mode, do you see drone capture the logs? If not, login to the machine where the runner is installed and run docker logs <container> for the container associated with your failed pipeline step. Does that include the expected logs?