[ 
https://issues.apache.org/jira/browse/OOZIE-1440?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13697109#comment-13697109
 ] 

Hadoop QA commented on OOZIE-1440:
----------------------------------

Testing JIRA OOZIE-1440

Cleaning local svn 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:green}+1{color} the patch does not introduce any line longer than 
132
.    {color:red}-1{color} the patch does not add/modify any testcase
{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: 1
.    Tests errors: 2

.    The patch failed the following testcases:

.      
testRequeueOnException(org.apache.oozie.command.coord.TestCoordPushDependencyCheckXCommand)

{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/640/
                
> Build fails in certain environments due to xerces OpenJPA issue
> ---------------------------------------------------------------
>
>                 Key: OOZIE-1440
>                 URL: https://issues.apache.org/jira/browse/OOZIE-1440
>             Project: Oozie
>          Issue Type: Bug
>          Components: build
>    Affects Versions: trunk
>            Reporter: Robert Kanter
>            Assignee: Sean Mackrory
>             Fix For: trunk
>
>         Attachments: 
> 0001-OOZIE-1440.-Build-fails-in-certain-environments-due-.patch, 
> 0001-OOZIE-1440.-Build-fails-in-certain-environments-due-.patch, 
> OOZIE-1440.patch
>
>
> We've been seeing some build failures on some machines due to an issue with 
> OpenJPA (specifically, the changes made in OOZIE-1377).  
> We see these two cryptic errors in the output from the build:
> {{[INFO] --- openjpa-maven-plugin:2.2.2:enhance (enhancer) @ oozie-core ---}}
> {{An error occurred while attempting to determine the version of 
> "file:/var/lib/jenkins/workspace/build/oozie/4.1.0-SNAPSHOT/source/core/target/classes/META-INF/persistence.xml".}}
> {{[ERROR] Failed to execute goal 
> org.apache.openjpa:openjpa-maven-plugin:2.2.2:enhance (enhancer) on project 
> oozie-core: Execution enhancer of goal 
> org.apache.openjpa:openjpa-maven-plugin:2.2.2:enhance failed: 
> org.apache.openjpa.persistence.PersistenceProductDerivation:java.lang.ClassCastException:
>  org.apache.xerces.parsers.XIncludeAwareParserConfiguration cannot be cast to 
> org.apache.xerces.xni.parser.XMLParserConfiguration -> [Help 1]}}
> I saw that RAVE-245 had a similar error and their solution was to add Xerces 
> as a dependency on the OpenJPA plugin.  This prevents a classpath env issue 
> from sometimes choosing the built-in buggy version of Xerces that Java is 
> using by default (see OOZIE-1017), and instead to use the better version that 
> we've been using elsewhere.  

--
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

Reply via email to