You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@flink.apache.org by "Chesnay Schepler (Jira)" <ji...@apache.org> on 2020/06/16 15:07:00 UTC

[jira] [Created] (FLINK-18334) Exclude .dumpstream files that only contain JAVA_TOOL_OPTIONS logging

Chesnay Schepler created FLINK-18334:
----------------------------------------

             Summary: 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
             Fix For: 1.11.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)