[
https://issues.apache.org/jira/browse/BEAM-10262?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17136128#comment-17136128
]
Brian Hulette commented on BEAM-10262:
--------------------------------------
This doesn't seem to be a universal problem. Here's a failure log that was not
truncated excessively:
https://builds.apache.org/job/beam_PreCommit_Java_Commit/11773/testReport/junit/org.apache.beam.runners.flink.translation.wrappers.streaming.io/UnboundedSourceWrapperTest$ParameterizedUnboundedSourceWrapperTest/testWatermarkEmission_numTasks___4__numSplits_2_/
> Jenkins truncates logs excessively for failing tests.
> -----------------------------------------------------
>
> Key: BEAM-10262
> URL: https://issues.apache.org/jira/browse/BEAM-10262
> Project: Beam
> Issue Type: Bug
> Components: build-system, testing
> Reporter: Brian Hulette
> Priority: P2
> Labels: infra
>
> 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.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
