We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
server, agent, web-ui
Pipeline steps will systematically fail with exit code 141 if the log size is over something between 2063600 and 2079000 bytes.
exit code 141
2063600
2079000
Here is how to test it.
The following pipeline will work:
pipeline: logs exec: image: bash commands: - bash -c "for i in {1..134}; do base64 /dev/urandom | head -n 200; done"
The following pipeline will not work (exit code 141):
pipeline: logs exec: image: bash commands: - bash -c "for i in {1..135}; do base64 /dev/urandom | head -n 200; done"
2063600 - 2079000 bytes range is given by:
2063600 - 2079000
for i in {1..134}; do base64 /dev/urandom | head -n 200; done >limit.log stat --format="%s" limit.log 2063600 for i in {1..135}; do base64 /dev/urandom | head -n 200; done >limit.log stat --format="%s" limit.log 2079000
This problem does not appear with docker agent, for instance, the following pipeline works without pb:
pipeline: generate log: image: debian:11-slim commands: - bash -c "for i in {1..400}; do base64 /dev/urandom | head -n 200; done"
But then, the log file seems to be trunkated to 2000000 bytes and it's impossible to download the full log from the web interface.
2000000
Server:
❯ docker images | grep woodpecker-server woodpeckerci/woodpecker-server next abdf33e30acc 35 hours ago 24.1MB
Local agent: Run from commit 08a9915, with go run ./cmd/agent --log-level debug
go run ./cmd/agent --log-level debug
Docker agent:
❯ docker images | grep woodpecker-agent woodpeckerci/woodpecker-agent next 374ee61b7354 35 hours ago 13.3MB
No response
The text was updated successfully, but these errors were encountered:
at the moment we use os Pipe but we should move to a buffer instead ... we do need it anyway as soon as we start using commands as list
Sorry, something went wrong.
https://github.com/woodpecker-ci/woodpecker/pull/1397/files#diff-a04c642ebae3a1409872e78fbebc32223305acdfb5ec9a67edf544176b000d82R43
556607b
Successfully merging a pull request may close this issue.
Component
server, agent, web-ui
Describe the bug
Pipeline steps will systematically fail with
exit code 141
if the log size is over something between2063600
and2079000
bytes.Here is how to test it.
The following pipeline will work:
The following pipeline will not work (
exit code 141
):2063600 - 2079000
bytes range is given by:This problem does not appear with docker agent, for instance, the following pipeline works without pb:
But then, the log file seems to be trunkated to
2000000
bytes and it's impossible to download the full log from the web interface.System Info
Server:
Local agent:
Run from commit 08a9915, with
go run ./cmd/agent --log-level debug
Docker agent:
Additional context
No response
Validations
The text was updated successfully, but these errors were encountered: