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

Hadoop QA commented on HBASE-13816:
-----------------------------------

{color:red}-1 overall{color}.  Here are the results of testing the latest 
attachment 
  http://issues.apache.org/jira/secure/attachment/12736382/hbase-13816_v1.patch
  against master branch at commit ae803d72fe3816378a9d2acd1775c01c9db19198.
  ATTACHMENT ID: 12736382

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

    {color:green}+0 tests included{color}.  The patch appears to be a 
documentation, build,
                        or dev-support patch that doesn't require tests.

    {color:green}+1 hadoop versions{color}. The patch compiles with all 
supported hadoop versions (2.4.1 2.5.2 2.6.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 site goal succeeds with this patch.

     {color:red}-1 core tests{color}.  The patch failed these unit tests:
                       org.apache.hadoop.hbase.backup.TestHFileArchiving
                  
org.apache.hadoop.hbase.mapreduce.TestLoadIncrementalHFilesUseSecurityEndPoint

     {color:red}-1 core zombie tests{color}.  There are 5 zombie test(s):       
at 
org.apache.phoenix.end2end.index.LocalIndexIT.testLocalIndexScanAfterRegionSplit(LocalIndexIT.java:735)
        at 
org.apache.phoenix.end2end.DeleteIT.testDeleteRowFromTableWithImmutableIndex(DeleteIT.java:371)
        at 
org.apache.phoenix.end2end.DeleteIT.testDeleteRowFromTableWithImmutableLocalIndex(DeleteIT.java:351)
        at 
org.apache.phoenix.end2end.index.IndexExpressionIT.testInClauseWithMutableIndex(IndexExpressionIT.java:560)

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

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

This message is automatically generated.

> Build shaded modules only in release profile
> --------------------------------------------
>
>                 Key: HBASE-13816
>                 URL: https://issues.apache.org/jira/browse/HBASE-13816
>             Project: HBase
>          Issue Type: Improvement
>            Reporter: Enis Soztutar
>            Assignee: Enis Soztutar
>             Fix For: 2.0.0, 1.2.0, 1.1.1
>
>         Attachments: hbase-13816_v1.patch
>
>
> Shaded modules are great, but not needed in the regular build + test cycle. I 
> noticed that around 30-40% of the build time goes in the actual shading. 
> I think we can just build the shaded jars in the {{release}} profile. 
> hadoopqe and mvn publishing should not be affected. 



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

Reply via email to