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
This happened for multiple builds after the system-recovery (so not a normal situation):
[2024-01-26 05:39:52,104][ INFO][PID:156605] Sending stomp bus message in build.end [2024-01-26 05:39:52,444][ INFO][PID:156605] Compressing backendresults/jdoe/foo/fedora-rawhide-aarch64/00110092-foo-workstation/builder-live.log by gzip [2024-01-26 05:39:52,447][ INFO][PID:156605] Running command 'gzip backendresults/jdoe/foo/fedora-rawhide-aarch64/00110092-foo-workstation/builder-live.log' as PID 161390 [2024-01-26 05:39:52,449][ INFO][PID:156605] Finished after 0 seconds with exit code 1 (gzip backendresults/jdoe/foo/fedora-rawhide-aarch64/00110092-foo-workstation/builder-live.log) stdout: stderr: gzip: backendresults/jdoe/foo/fedora-rawhide-aarch64/00110092-foo-workstation/builder-live.log: No such file or directory [2024-01-26 05:39:52,450][ ERROR][PID:156605] Unable to compress file backendresults/jdoe/foo/fedora-rawhide-aarch64/00110092-foo-workstation/builder-live.log [2024-01-26 05:39:52,451][ INFO][PID:156605] Compressing backendresults/jdoe/foo/fedora-rawhide-aarch64/00110092-foo-workstation/backend.log by gzip
But anyway, we should never end up with failed builds like that. Users have to retrigger builds, etc.
The text was updated successfully, but these errors were encountered:
Triage: The builder-live.log didn't exist, so we shouldn't have tried to gzip it. Maybe some retry should have happened.
builder-live.log
Sorry, something went wrong.
No branches or pull requests
This happened for multiple builds after the system-recovery (so not a normal
situation):
But anyway, we should never end up with failed builds like that. Users have to
retrigger builds, etc.
The text was updated successfully, but these errors were encountered: