[GitHub] [beam] damccorm opened a new issue, #20342: Jenkins truncates logs excessively for failing tests.

[GitBox <gi...@apache.org>]

damccorm opened a new issue, #20342:
URL: https://github.com/apache/beam/issues/20342

   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](https://github.com/jenkinsci/junit-plugin/blob/master/src/main/java/hudson/tasks/junit/CaseResult.java#L190) 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](https://issues.apache.org/jira/browse/BEAM-10262). Original Jira may contain additional context.
   Reported by: bhulette.


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: github-unsubscribe@beam.apache.org.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org

Re: [I] Jenkins truncates logs excessively for failing tests. [beam]

["Abacn (via GitHub)" <gi...@apache.org>]

Abacn closed issue #20342: Jenkins truncates logs excessively for failing tests.
URL: https://github.com/apache/beam/issues/20342


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: github-unsubscribe@beam.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org