You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@oozie.apache.org by "Hadoop QA (JIRA)" <ji...@apache.org> on 2012/09/04 19:31:07 UTC
[jira] [Commented] (OOZIE-973) Allow Oozie to run against Hadoop
trunk branch
[ https://issues.apache.org/jira/browse/OOZIE-973?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13447831#comment-13447831 ]
Hadoop QA commented on OOZIE-973:
---------------------------------
Testing JIRA OOZIE-973
Cleaning local svn workspace
{code}
----------------------------
+1 PATCH_APPLIES
CLEAN cleaned target directories
-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 seems to introduce 11 new javac warning(s)
+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: 904
Tests failures: 1
Tests errors: 0
+1 DISTRO
+1 distro tarball builds with the patch
----------------------------
{code}
The full output of the test-patch run is available at
https://builds.apache.org/job/oozie-trunk-precommit-build/80/
> Allow Oozie to run against Hadoop trunk branch
> ----------------------------------------------
>
> Key: OOZIE-973
> URL: https://issues.apache.org/jira/browse/OOZIE-973
> Project: Oozie
> Issue Type: Improvement
> Affects Versions: trunk
> Reporter: Robert Kanter
> Assignee: Robert Kanter
> Priority: Minor
> Attachments: OOZIE-973.patch
>
>
> Modify the poms to allow Oozie to run against the Hadoop trunk branch (with a command line argument or some other mechanism)
--
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