[
https://issues.apache.org/jira/browse/BIGTOP-1113?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13792656#comment-13792656
]
jay vyas commented on BIGTOP-1113:
----------------------------------
Thanks alot kons. This will be useful. Now - may i ask why not using SLF4J ?
Might be a good modification since its what hadoop uses.
IIRC , SLF4J is easy to configure because it has a deterministic logging setup:
It just finds the SLF4J binding in the classpath directly. That means that the
pom file log properties will be self describing - the underlying logging
library will be a dependency in the pom rather than found magically on the
classpath.
What do y'all think about swapping in SL4J for commons logging.
> 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)
