[
https://issues.apache.org/jira/browse/OOZIE-1332?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13634700#comment-13634700
]
Hadoop QA commented on OOZIE-1332:
----------------------------------
Testing JIRA OOZIE-1332
Cleaning local svn workspace
----------------------------
{color:green}+1 PATCH_APPLIES{color}
{color:green}+1 CLEAN{color}
{color:green}+1 RAW_PATCH_ANALYSIS{color}
. {color:green}+1{color} the patch does not introduce any @author tags
. {color:green}+1{color} the patch does not introduce any tabs
. {color:green}+1{color} the patch does not introduce any trailing spaces
. {color:green}+1{color} the patch does not introduce any line longer than
132
. {color:green}+1{color} the patch does adds/modifies 1 testcase(s)
{color:green}+1 RAT{color}
. {color:green}+1{color} the patch does not seem to introduce new RAT
warnings
{color:green}+1 JAVADOC{color}
. {color:green}+1{color} the patch does not seem to introduce new Javadoc
warnings
{color:green}+1 COMPILE{color}
. {color:green}+1{color} HEAD compiles
. {color:green}+1{color} patch compiles
. {color:green}+1{color} the patch does not seem to introduce new javac
warnings
{color:green}+1 BACKWARDS_COMPATIBILITY{color}
. {color:green}+1{color} the patch does not change any JPA
Entity/Colum/Basic/Lob/Transient annotations
. {color:green}+1{color} the patch does not modify JPA files
{color:red}-1 TESTS{color}
. Tests run: 1107
. Tests failed: 1
. Tests errors: 0
. The patch failed the following testcases:
.
testEvictionOnTimeToIdle(org.apache.oozie.service.TestPartitionDependencyManagerEhcache)
{color:green}+1 DISTRO{color}
. {color:green}+1{color} distro tarball builds with the patch
----------------------------
{color:red}*-1 Overall result, please check the reported -1(s)*{color}
The full output of the test-patch run is available at
. https://builds.apache.org/job/oozie-trunk-precommit-build/450/
> Flakey test TestActionCheckXCommand.testActionCheckTransientDuringMRAction
> --------------------------------------------------------------------------
>
> Key: OOZIE-1332
> URL: https://issues.apache.org/jira/browse/OOZIE-1332
> Project: Oozie
> Issue Type: Bug
> Components: tests
> Affects Versions: trunk, 3.3.2, 4.0.0
> Reporter: Robert Kanter
> Assignee: Robert Kanter
> Fix For: trunk, 4.0.0
>
> Attachments: OOZIE-1332.patch
>
>
> We've been seeing
> TestActionCheckXCommand.testActionCheckTransientDuringMRAction as flakey on
> our CI tests.
> This incorrect sequence of events was occurring:
> {noformat}
> ...
> - ActionCheckXCommand start
> - suspend WF
> - ActionCheckXCommand end
> - ActionCheckXCommand start
> - JT up
> - unknown hadoop job error
> - fail WF
> - ActionCheckXCommand end
> - ResumeXCommand cannot start (because WF fail)
> - test finish
> {noformat}
> when this correct sequence of events should have been occuring:
> {noformat}
> ...
> - ActionCheckXCommand start
> - suspend WF
> - ActionCheckXCommand end
> - JT Up
> - ResumeXCommand start
> - ResumeXCommand end
> - ActionStartXCommand start
> - ActionStartXCommadn end
> - ActionCheckXCommand start
> - ActionCheckXCommand end
> ...
> - test finish
> {noformat}
> It turns out that the ActionCheckerService was triggering an extra
> ActionCheckXCommand at just the wrong moment. We should disable the
> ActionCheckerService during this test to prevent this issue (When I
> originally wrote the test, I incorrectly thought it was needed and that it
> had to run more frequently to make the test faster).
> As a pre-emptive measure, we should also do this for
> TestActionCheckXCommand.testActionCheckTransientDuringLauncher, which is very
> similar even though we didn't see any flakiness.
--
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
