[
https://issues.apache.org/jira/browse/BIGTOP-1113?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Konstantin Boudnik updated BIGTOP-1113:
---------------------------------------
Affects Version/s: 0.7.0
> 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
> Affects Versions: 0.7.0
> Reporter: jay vyas
> Attachments: JUST_AN_EXAMPLE_SLF4J.patch
>
>
> 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.2#6252)
