Skip to content
New issue

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

Jenkins truncates logs excessively for failing tests. #20342

Closed
damccorm opened this issue Jun 4, 2022 · 0 comments
Closed

Jenkins truncates logs excessively for failing tests. #20342

damccorm opened this issue Jun 4, 2022 · 0 comments

Comments

@damccorm
Copy link
Contributor

damccorm commented Jun 4, 2022

More background info in https://issues.apache.org/jira/browse/BEAM-9976?focusedCommentId=17134617&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-17134617

The code for the jenkins junit plugin indicates stdout/stderr logs should be truncated to 1MiB for failing runs, and just 1 KiB for passing runs. However all Beam tests seem to be truncated to 1 KiB, not just passing runs. This can make it very difficult to debug flaky tests, since they are challenging to reproduce locally, and nearly all the relevant information from the failures is removed.

Imported from Jira BEAM-10262. Original Jira may contain additional context.
Reported by: bhulette.

@Abacn Abacn closed this as not planned Won't fix, can't repro, duplicate, stale Feb 21, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants