[
https://issues.apache.org/jira/browse/OOZIE-2228?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14695959#comment-14695959
]
Hadoop QA commented on OOZIE-2228:
----------------------------------
Testing JIRA OOZIE-2228
Cleaning local git workspace
----------------------------
{color:green}+1 PATCH_APPLIES{color}
{color:green}+1 CLEAN{color}
{color:red}-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:red}-1{color} the patch contains 2 line(s) longer than 132
characters
. {color:green}+1{color} the patch does adds/modifies 2 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: 1686
. Tests failed: 3
. Tests errors: 0
. The patch failed the following testcases:
. testWrongHost(org.apache.oozie.service.TestProxyUserService)
.
testNone(org.apache.oozie.command.coord.TestCoordActionInputCheckXCommandNonUTC)
.
testCoordMaterializeTriggerService3(org.apache.oozie.service.TestCoordMaterializeTriggerService)
{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/2499/
> Statustransit service doesn't pick bundle with suspend status
> -------------------------------------------------------------
>
> Key: OOZIE-2228
> URL: https://issues.apache.org/jira/browse/OOZIE-2228
> Project: Oozie
> Issue Type: Bug
> Reporter: Purshotam Shah
> Assignee: Purshotam Shah
> Attachments: OOZIE-2228-V1.patch, OOZIE-2228-V2.patch,
> OOZIE-2228-V3.patch
>
>
> {code}
> @NamedQuery(name = "GET_BUNDLE_IDS_FOR_STATUS_TRANSIT", query = "select
> DISTINCT w.id from BundleActionBean a , BundleJobBean w where
> a.lastModifiedTimestamp >= :lastModifiedTime and w.id = a.bundleId and
> (w.statusStr = 'RUNNING' OR w.statusStr = 'RUNNINGWITHERROR' OR w.statusStr =
> 'PAUSED' OR w.statusStr = 'PAUSEDWITHERROR' OR w.pending = 1)"),
> {code}
> Can be reproduced easily.
> 1. suspend coord, bundle goes to suspend by StatusTransitService.
> 2. resume coord, bundle remains in suspend state.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
