[
https://issues.apache.org/jira/browse/BIGTOP-1113?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13803215#comment-13803215
]
jay vyas commented on BIGTOP-1113:
----------------------------------
FYI: From my tests, it appears that the only work to be done is just
(1) decide on what logging frameowrk is best, and
(2) add the slf4j binding for it if its not already there (appears that bigtop
already has slf4j-simple bindings :
http://www.slf4j.org/api/org/slf4j/impl/SimpleLogger.html, so no work is really
even needed here).
(3) start updating all the smokes to use SLF4J .
The advantage will be that there is no direct API coupling to the old commons
logging in the bigtop smokes anymore, and people can use the more common, easy
to configure / debug SLF4J bindings.
> 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)
