[
https://issues.apache.org/jira/browse/FLINK-18334?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17327767#comment-17327767
]
Flink Jira Bot commented on FLINK-18334:
----------------------------------------
This major issue is unassigned and itself and all of its Sub-Tasks have not
been updated for 30 days. So, it has been labeled "stale-major". If this ticket
is indeed "major", please either assign yourself or give an update. Afterwards,
please remove the label. In 7 days the issue will be deprioritized.
> Exclude .dumpstream files that only contain JAVA_TOOL_OPTIONS logging
> ---------------------------------------------------------------------
>
> Key: FLINK-18334
> URL: https://issues.apache.org/jira/browse/FLINK-18334
> Project: Flink
> Issue Type: Bug
> Components: Build System / CI
> Reporter: Chesnay Schepler
> Priority: Major
> Labels: stale-major
> Fix For: 1.13.0
>
>
> For debugging purposes we tell all JVMs on CI to create a heap dump if they
> hit an OOM.
> We additionally collect the .dumpstream files from surefire, which contain
> the raw JVM output.
> All JVMs will log something like this:
> {code}
> # Created at 2020-06-16T14:30:35.624
> Picked up JAVA_TOOL_OPTIONS: -XX:+HeapDumpOnOutOfMemoryError
> {code}
> This is fine, and cannot be avoided, but as a result you have a lot of
> .dumpstream files that only contain this entry, which is a bit annoying when
> looking for that one file that actually contains the important entries.
> Maybe we could filter out files that only contain these entries.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
