[
https://issues.apache.org/jira/browse/BIGTOP-1113?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13803208#comment-13803208
]
jay vyas commented on BIGTOP-1113:
----------------------------------
I added a patch that shows how SLF4J logs will work by embedding the groovy
script in the pom.
you can play with it by just runnnig :
"mvn clean test package -f bigtop-tests/test-artifacts/pom.xml 2>&1 | grep LOG "
And you will see the SLF4J logs come out.
> 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
> 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.1#6144)
