[
https://issues.apache.org/jira/browse/BEAM-10262?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17178317#comment-17178317
]
Beam JIRA Bot commented on BEAM-10262:
--------------------------------------
This issue is P2 but has been unassigned without any comment for 60 days so it
has been labeled "stale-P2". If this issue is still affecting you, we care!
Please comment and remove the label. Otherwise, in 14 days the issue will be
moved to P3.
Please see https://beam.apache.org/contribute/jira-priorities/ for a detailed
explanation of what these priorities mean.
> 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, stale-P2
>
> 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)
