hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Mike Drob (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-18285) Failsafe ITs very noisy output to stdout
Date Fri, 07 Jul 2017 07:16:00 GMT

    [ https://issues.apache.org/jira/browse/HBASE-18285?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16077729#comment-16077729
] 

Mike Drob commented on HBASE-18285:
-----------------------------------

I'm not sure what changed, but in my environment this now outputs

{noformat}
[WARNING] Corrupted stdin stream in forked JVM 1. See the dump file /Users/mdrob/IdeaProjects/hbase/hbase-spark-it/target/failsafe-reports/2017-07-07T00-07-38_980-jvmRun1.dumpstream
{noformat}

which is both better and worse

> Failsafe ITs very noisy output to stdout
> ----------------------------------------
>
>                 Key: HBASE-18285
>                 URL: https://issues.apache.org/jira/browse/HBASE-18285
>             Project: HBase
>          Issue Type: Bug
>          Components: integration tests
>            Reporter: Mike Drob
>
> Way back in HBASE-14819 our Stack added some flags to our failsafe plugin runs to print
more debugging information. This information is very useful, but should not be going to the
console when we run ITs.
> The culprit flags are 
> {{-XX:+PrintCommandLineFlags -XX:+PrintFlagsFinal -XX:+PrintGC}}
> If we want to have this information available, then we should send it off to a file.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

Mime
View raw message