Details
-
Test
-
Status: Closed
-
Minor
-
Resolution: Fixed
-
None
-
None
-
None
-
Reviewed
Description
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 :
HBASE-14286patch 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}
https://builds.apache.org/job/PreCommit-HBASE-Build/15250/console :
HBASE-14268patch 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}
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.