Missing pipeline status when pod complete too fast on k8s backend

[eliasscosta]

Component

agent

Describe the bug

Sometimes pod run too fast and it's impossible to woodpecker-agent get the status and log.

State:          Terminated
Reason:       Completed
Exit Code:    0
Started:      Wed, 06 Mar 2024 12:45:54 -0300
Finished:     Wed, 06 Mar 2024 12:45:56 -0300

When pod did it the pipeline/step continue running forever until someone decide to cancel.

System Info

{"source":"https://github.com/woodpecker-ci/woodpecker","version":"2.3.0"}

Additional context

No response

Validations

• Read the docs.
• Check that there isn't already an issue that reports the same bug to avoid creating a duplicate.
• Checked that the bug isn't fixed in the next version already [https://woodpecker-ci.org/faq#which-version-of-woodpecker-should-i-use]

[eliasscosta]

Applying a workaround solution such as adding a sleep command, we realized that the issue is not related to the pod terminating too quickly, but rather to how the agent parses the logs. When we modified the output to be as plain text as possible, the step started to finish correctly.

[eliasscosta]

We tested setting the agent to run a small number of workflows (2 workflows per agent) with limited CPU resources, then we discovered we suffer the same issue described here: #2253 After we applied the fix to it we do not see this behavior anymore.