You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The text was updated successfully, but these errors were encountered:
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.
The text was updated successfully, but these errors were encountered: