[
https://issues.apache.org/jira/browse/OOZIE-1379?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13696067#comment-13696067
]
Hadoop QA commented on OOZIE-1379:
----------------------------------
Testing JIRA OOZIE-1379
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 13 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: 1255
. Tests failed: 3
. Tests errors: 5
. The patch failed the following testcases:
. testStreamLog4JobLogDate(org.apache.oozie.TestCoordinatorEngineStreamLog)
. testBundleKill2(org.apache.oozie.command.bundle.TestBundleKillXCommand)
.
testCoordKillRemovePushMissingDeps(org.apache.oozie.command.coord.TestCoordKillXCommand)
{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/638/
> Generate SLA end_miss event only after confirming against persistent store
> --------------------------------------------------------------------------
>
> Key: OOZIE-1379
> URL: https://issues.apache.org/jira/browse/OOZIE-1379
> Project: Oozie
> Issue Type: Sub-task
> Reporter: Mona Chitnis
> Assignee: Mona Chitnis
> Attachments: OOZIE-1379.patch, OOZIE-1379.patch
>
>
> 1. SLA status "MISS" which occurs on an END_MISS i.e. job overshot expected
> end time, is the most important sla notification for the user. We should make
> sure against the source of truth i.e. database, that the scenario is indeed
> correct for an end_miss, before setting the SLA status and sending out alerts
> for it
> 2. hanging job id getter and setter in SLASummaryBean to getId and setId to
> be consistent with getter in SLARegistrationBean
> 3. Fix bug where when Coordinator action goes from WAITING->KILLED directly,
> no event is received
--
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
