[
https://issues.apache.org/jira/browse/FALCON-32?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jarek Jarcec Cecho updated FALCON-32:
-------------------------------------
Attachment: bugFALCON-32.patch
I've investigated failures in {{common}} module and it seems that some tests
were not cleaning up properly whereas the next test was not able to pick the
unclean stuff. The issue did not surface before because the initialization in
question is defined with {{@BeforeClass}} annotation. As a result it was called
only once for all tests before the surefire reconfiguration and for every
single testcase after the reconfiguration.
I do see additional failures issues in Oozie module that I'll further
investigate. The patch is still not ready to be committed.
> Store test output in file rather then printing all the output into the console
> ------------------------------------------------------------------------------
>
> Key: FALCON-32
> URL: https://issues.apache.org/jira/browse/FALCON-32
> Project: Falcon
> Issue Type: Improvement
> Components: general
> Affects Versions: 0.3
> Reporter: Jarek Jarcec Cecho
> Assignee: Jarek Jarcec Cecho
> Priority: Trivial
> Fix For: 0.3
>
> Attachments: bugFALCON-32.patch, bugFALCON-32.patch,
> bugFALCON-32.patch
>
>
> Current build is printing all output into console, messing maven and test
> outputs together. Also having everything in console makes test failure
> investigation complicated. One still could redirect output of entire maven
> command to file and investigate it there, but this seems to be unnecessary
> and therefore I would like to propose taking advantage of surefire feature to
> redirect the test output into files.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
