hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hadoop QA (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-14337) build error on master
Date Mon, 31 Aug 2015 14:03:45 GMT

    [ https://issues.apache.org/jira/browse/HBASE-14337?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14723428#comment-14723428

Hadoop QA commented on HBASE-14337:

{color:red}-1 overall{color}.  Here are the results of testing the latest attachment 
  against master branch at commit df341c4299ea21e4e1ca09652f6126633f2307c5.
  ATTACHMENT ID: 12753288

    {color:green}+1 @author{color}.  The patch does not contain any @author tags.

    {color:red}-1 tests included{color}.  The patch doesn't appear to include any new or modified
                        Please justify why no new tests are needed for this patch.
                        Also please list what manual steps were performed to verify this patch.

    {color:green}+1 hadoop versions{color}. The patch compiles with all supported hadoop versions
(2.4.0 2.4.1 2.5.0 2.5.1 2.5.2 2.6.0 2.7.0 2.7.1)

    {color:green}+1 javac{color}.  The applied patch does not increase the total number of
javac compiler warnings.

    {color:green}+1 protoc{color}.  The applied patch does not increase the total number of
protoc compiler warnings.

    {color:green}+1 javadoc{color}.  The javadoc tool did not generate any warning messages.

    {color:green}+1 checkstyle{color}.  The applied patch does not increase the total number
of checkstyle errors

    {color:red}-1 findbugs{color}.  The patch appears to cause Findbugs (version 2.0.3) to

    {color:green}+1 release audit{color}.  The applied patch does not increase the total number
of release audit warnings.

    {color:green}+1 lineLengths{color}.  The patch does not introduce lines longer than 100

    {color:red}-1 site{color}.  The patch appears to cause mvn post-site goal to fail.

     {color:red}-1 core tests{color}.  The patch failed these unit tests:

Test results: https://builds.apache.org/job/PreCommit-HBASE-Build/15340//testReport/
Checkstyle Errors: https://builds.apache.org/job/PreCommit-HBASE-Build/15340//artifact/patchprocess/checkstyle-aggregate.html

  Console output: https://builds.apache.org/job/PreCommit-HBASE-Build/15340//console

This message is automatically generated.

> build error on master
> ---------------------
>                 Key: HBASE-14337
>                 URL: https://issues.apache.org/jira/browse/HBASE-14337
>             Project: HBase
>          Issue Type: Bug
>            Reporter: Gabor Liptak
>            Assignee: Sean Busbey
>         Attachments: HBASE-14227_v5.patch, HBASE-14337.1.patch
> In https://builds.apache.org/job/PreCommit-HBASE-Build/15325//console
> /home/jenkins/tools/maven/latest/bin/mvn clean package checkstyle:checkstyle-aggregate
findbugs:findbugs -DskipTests  -DHBasePatchProcess > /home/jenkins/jenkins-slave/workspace/PreCommit-HBASE-Build/patchprocess/trunkJavacWarnings.txt
> mvn exit code was 0
> mv: cannot stat 'target/checkstyle-result.xml': No such file or directory
> Usage: edu.umd.cs.findbugs.workflow.UnionResults [options] [<results1> <results2>
... <resultsn>] 
> Expected 2...2147483647 file arguments, found 1
> Options:
>     -withMessages        Generated XML should contain msgs for external processing
>     -output <outputFile> File in which to store combined results
> Exception in thread "main" java.io.FileNotFoundException: /home/jenkins/jenkins-slave/workspace/PreCommit-HBASE-Build/patchprocess/trunkFindbugsWarnings.xml
(No such file or directory)
> 	at java.io.FileInputStream.open(Native Method)
> 	at java.io.FileInputStream.<init>(FileInputStream.java:146)
> 	at edu.umd.cs.findbugs.SortedBugCollection.progessMonitoredInputStream(SortedBugCollection.java:1231)
> 	at edu.umd.cs.findbugs.SortedBugCollection.readXML(SortedBugCollection.java:308)
> 	at edu.umd.cs.findbugs.SortedBugCollection.readXML(SortedBugCollection.java:295)
> 	at edu.umd.cs.findbugs.PrintingBugReporter.xslt(PrintingBugReporter.java:235)
> 	at edu.umd.cs.findbugs.PrintingBugReporter.main(PrintingBugReporter.java:159)
> /home/jenkins/jenkins-slave/workspace/PreCommit-HBASE-Build/patchprocess/trunkFindbugsWarnings.xml:
 ERROR: cannot open `/home/jenkins/jenkins-slave/workspace/PreCommit-HBASE-Build/patchprocess/trunkFindbugsWarnings.xml'
(No such file or directory)
> /home/jenkins/jenkins-slave/workspace/PreCommit-HBASE-Build/patchprocess/trunkFindbugsWarnings.html:
ERROR: cannot open `/home/jenkins/jenkins-slave/workspace/PreCommit-HBASE-Build/patchprocess/trunkFindbugsWarnings.html'
(No such file or directory)
> /home/jenkins/tools/maven/latest/bin/mvn clean install -DskipTests -DHBasePatchProcess
-Dhadoop-two.version=2.4.0 > /home/jenkins/jenkins-slave/workspace/PreCommit-HBASE-Build/patchprocess/patchJavacWithHadoop-2.4.0.txt
> ======================================================================
> There are compilation errors with Hadoop version 2.4.0.
> ======================================================================
> [ERROR] Error invoking method 'get(java.lang.Integer)' in java.util.ArrayList at META-INF/LICENSE.vm[line
1619, column 22]
> [ERROR] Failed to execute goal org.apache.maven.plugins:maven-remote-resources-plugin:1.5:process
(default) on project hbase-assembly: Error rendering velocity resource. Error invoking method
'get(java.lang.Integer)' in java.util.ArrayList at META-INF/LICENSE.vm[line 1619, column 22]:
InvocationTargetException: Index: 0, Size: 0 -> [Help 1]
> [ERROR] 
> [ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch.
> [ERROR] Re-run Maven using the -X switch to enable full debug logging.
> [ERROR] 
> [ERROR] For more information about the errors and possible solutions, please read the
following articles:
> [ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionException
> [ERROR] 
> [ERROR] After correcting the problems, you can resume the build with the command
> [ERROR]   mvn <goals> -rf :hbase-assembly

This message was sent by Atlassian JIRA

View raw message