[
https://issues.apache.org/jira/browse/OOZIE-2648?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15470468#comment-15470468
]
Abhishek Bafna commented on OOZIE-2648:
---------------------------------------
Commenting the jenkins report manually, as jenkins failed to comment it.
--------------------------- {{Jenkins Report}} ---------------------------
Testing JIRA OOZIE-2648
Cleaning local git workspace
----------------------------
+1 PATCH_APPLIES
+1 CLEAN
-1 RAW_PATCH_ANALYSIS
+1 the patch does not introduce any @author tags
+1 the patch does not introduce any tabs
+1 the patch does not introduce any trailing spaces
+1 the patch does not introduce any line longer than 132
-1 the patch does not add/modify any testcase
+1 RAT
+1 the patch does not seem to introduce new RAT warnings
+1 JAVADOC
+1 the patch does not seem to introduce new Javadoc warnings
+1 COMPILE
+1 HEAD compiles
+1 patch compiles
+1 the patch does not seem to introduce new javac warnings
+1 BACKWARDS_COMPATIBILITY
+1 the patch does not change any JPA Entity/Colum/Basic/Lob/Transient
annotations
+1 the patch does not modify JPA files
-1 TESTS
Tests run: 1800
Tests failed: 3
Tests errors: 1
The patch failed the following testcases:
testNone(org.apache.oozie.command.coord.TestCoordActionInputCheckXCommand)
testBundleId(org.apache.oozie.servlet.TestBulkMonitorWebServiceAPI)
testNone(org.apache.oozie.command.coord.TestCoordActionInputCheckXCommandNonUTC)
+1 DISTRO
+1 distro tarball builds with the patch
----------------------------
-1 Overall result, please check the reported -1(s)
The full output of the test-patch run is available at
https://builds.apache.org/job/oozie-trunk-precommit-build/3264/
--------------------------- {{Jenkins Error While Reporting}}
---------------------------
mv: cannot stat 'jira-cli-2.6.0': No such file or directory
chmod: cannot access
'/home/jenkins/jenkins-slave/workspace/oozie-trunk-precommit-build/test-patch/tools/jira-cli/jira.sh':
No such file or directory
Adding comment to JIRA
bin/test-patch: line 124:
/home/jenkins/jenkins-slave/workspace/oozie-trunk-precommit-build/test-patch/tools/jira-cli/jira.sh:
No such file or directory
test-patch exit code: 1
Build step 'Execute shell' marked build as failure
Archiving artifacts
Recording test results
Sending e-mails to: dev@oozie.apache.org
Finished: FAILURE
> Child jobs shouldn't send callbacks to Oozie
> --------------------------------------------
>
> Key: OOZIE-2648
> URL: https://issues.apache.org/jira/browse/OOZIE-2648
> Project: Oozie
> Issue Type: Improvement
> Affects Versions: trunk
> Reporter: Robert Kanter
> Assignee: Abhishek Bafna
> Attachments: OOZIE-2648-00.patch
>
>
> I noticed that all action.xml files end up having
> {{job.end.notification.url}} set to send the callback to the Oozie Server
> when they finish. This makes it so that all child MR jobs have this, and
> send notifications to the Oozie Server. This isn't the end of the world, but
> it's unnecessary, especially if you end up with multiple child jobs (e.g. a
> Hive Action that spawns multiple MR jobs). We should consider only adding it
> to the Launcher Job. The exception to this is the MapReduce Action, where
> the Launcher Job exits early and Oozie directly monitors the MR child; in
> this case, the child should have it and the Launcher should not.
> The call in {{JavaActionExecutor}} to {{injectActionCallback(context,
> actionConf);}} is where this happens.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
