hbase-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Ted Yu (JIRA)" <j...@apache.org>
Subject [jira] [Created] (HBASE-14310) test-patch.sh should handle spurious non-zero exit code from maven
Date Tue, 25 Aug 2015 23:08:45 GMT
Ted Yu created HBASE-14310:
------------------------------

             Summary: test-patch.sh should handle spurious non-zero exit code from maven
                 Key: HBASE-14310
                 URL: https://issues.apache.org/jira/browse/HBASE-14310
             Project: HBase
          Issue Type: Test
            Reporter: Ted Yu
            Assignee: Ted Yu
            Priority: Minor
         Attachments: 14310-v1.txt

Starting last weekend, I saw patch testing abort due to spurious non-zero exit code from maven.

Here are recent examples.
https://builds.apache.org/job/PreCommit-HBASE-Build/15251/console :
{code}
HBASE-14286 patch is being downloaded at Tue Aug 25 18:49:17 UTC 2015 from
http://issues.apache.org/jira/secure/attachment/12751767/HBASE-14286.1.patch
...
/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
2>&1
Trunk compilation is broken?
    \{code\}\{code\}
{code}
https://builds.apache.org/job/PreCommit-HBASE-Build/15250/console :
{code}
HBASE-14268 patch is being downloaded at Tue Aug 25 18:19:25 UTC 2015 from
http://issues.apache.org/jira/secure/attachment/12752280/14268-V5.patch
...
/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
2>&1
Trunk compilation is broken?
    \{code\}\{code\}
{code}
The search in mvn output for 'Compilation failure' returned nothing.
I verified locally that with 14268-V5.patch, master branch compiled.

test-patch.sh should handle the spurious exit code so that patches can be tested.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message