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-14310) test-patch.sh should handle spurious non-zero exit code from maven
Date Wed, 26 Aug 2015 01:56:45 GMT

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

Hadoop QA commented on HBASE-14310:
-----------------------------------

{color:red}-1 overall{color}.  Here are the results of testing the latest attachment 
  http://issues.apache.org/jira/secure/attachment/12752346/14310-v1.txt
  against master branch at commit 44caba31e4f259ea82d5141d2ba40a6d98f14f61.
  ATTACHMENT ID: 12752346

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

    {color:green}+1 tests included{color}.  The patch appears to include 3 new or modified
tests.

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

    {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:green}+1 findbugs{color}.  The patch does not introduce any  new Findbugs (version
2.0.3) warnings.

    {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:green}+1 site{color}.  The mvn post-site goal succeeds with this patch.

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

     {color:red}-1 core zombie tests{color}.  There are 10 zombie test(s): 	at org.apache.hadoop.hbase.mapreduce.TestHFileOutputFormat.testExcludeMinorCompaction(TestHFileOutputFormat.java:1042)
	at org.apache.hadoop.hbase.snapshot.TestMobExportSnapshot.testExportFailure(TestMobExportSnapshot.java:314)
	at org.apache.hadoop.hbase.mapreduce.TestTimeRangeMapRed.testTimeRangeMapRed(TestTimeRangeMapRed.java:163)
	at org.apache.hadoop.hbase.client.TestHCM.testConnectionClose(TestHCM.java:398)
	at org.apache.hadoop.hbase.client.TestHCM.testConnectionCloseAllowsInterrupt(TestHCM.java:281)
	at org.apache.hadoop.hbase.mapreduce.TestImportTSVWithVisibilityLabels.testBulkOutputWithTsvImporterTextMapper(TestImportTSVWithVisibilityLabels.java:254)
	at org.apache.hadoop.hbase.mapreduce.TestCopyTable.testCopyTableWithBulkload(TestCopyTable.java:131)

Test results: https://builds.apache.org/job/PreCommit-HBASE-Build/15255//testReport/
Release Findbugs (version 2.0.3) 	warnings: https://builds.apache.org/job/PreCommit-HBASE-Build/15255//artifact/patchprocess/newFindbugsWarnings.html
Checkstyle Errors: https://builds.apache.org/job/PreCommit-HBASE-Build/15255//artifact/patchprocess/checkstyle-aggregate.html

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

This message is automatically generated.

> 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 :
> {quote}
> 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\}
> {quote}
> https://builds.apache.org/job/PreCommit-HBASE-Build/15250/console :
> {quote}
> 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\}
> {quote}
> 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