[jira] [Comment Edited] (BIGTOP-1113) Failing smokes should copy Std Error / Std Out to a file or else print them to the existing test logs.

["jay vyas (JIRA)" <ji...@apache.org>]

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

jay vyas edited comment on BIGTOP-1113 at 10/10/13 10:21 PM:
-------------------------------------------------------------

Ah yes great point.  I see in the Shell class: 
[code]
    if (LOG.isTraceEnabled()) {
        LOG.trace("${shell} << __EOT__\n${script}\n__EOT__");
    }

[/code]

So Its just a matter of making sure TRACE is enabled.  Im pretty sure this is just the global maven parameter?  Will experiment some and post here.


was (Author: jayunit100):
Ah yes great point.  I see in the Shell class: 

    if (LOG.isTraceEnabled()) {
        LOG.trace("${shell} << __EOT__\n${script}\n__EOT__");
    }

So Its just a matter of making sure TRACE is enabled.  Im pretty sure this is just the global maven parameter?  Will experiment some and post here.

> Failing smokes should copy Std Error / Std Out to a file or else print them to the existing test logs.
> ------------------------------------------------------------------------------------------------------
>
>                 Key: BIGTOP-1113
>                 URL: https://issues.apache.org/jira/browse/BIGTOP-1113
>             Project: Bigtop
>          Issue Type: Bug
>          Components: Tests
>            Reporter: jay vyas
>
> It is a useful feature that bigtop test framework ITest already captures std out / std err rather than streaming it to screen......... but if the direct std output/error from the client invoking a job was printed to the test outputs in failsafe.  
> In general these outputs arent necessary and clutter test reports , but in cases of low level or system failures, the specific assertion failures arent particularly helpful.
> Before adding a patch, i wonder : another option Could we add a top level maven parameter to tell iTest to redirect std err /std out?



--
This message was sent by Atlassian JIRA
(v6.1#6144)