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-8286) Move site back up out of hbase-assembly; bad idea
Date Sun, 07 Apr 2013 05:41:19 GMT

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

Hadoop QA commented on HBASE-8286:
----------------------------------

{color:red}-1 overall{color}.  Here are the results of testing the latest attachment 
  http://issues.apache.org/jira/secure/attachment/12577427/8286.txt
  against trunk revision .

    {color:red}-1 @author{color}.  The patch appears to contain 2 @author tags which the Hadoop
community has agreed to not allow in code contributions.

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

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

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

    {color:green}+1 findbugs{color}.  The patch does not introduce any new Findbugs (version
1.3.9) warnings.

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

    {color:red}-1 lineLengths{color}.  The patch introduces 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.zookeeper.lock.TestZKInterProcessReadWriteLock

Test results: https://builds.apache.org/job/PreCommit-HBASE-Build/5167//testReport/
Findbugs warnings: https://builds.apache.org/job/PreCommit-HBASE-Build/5167//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-protocol.html
Findbugs warnings: https://builds.apache.org/job/PreCommit-HBASE-Build/5167//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-client.html
Findbugs warnings: https://builds.apache.org/job/PreCommit-HBASE-Build/5167//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-examples.html
Findbugs warnings: https://builds.apache.org/job/PreCommit-HBASE-Build/5167//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-hadoop1-compat.html
Findbugs warnings: https://builds.apache.org/job/PreCommit-HBASE-Build/5167//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-prefix-tree.html
Findbugs warnings: https://builds.apache.org/job/PreCommit-HBASE-Build/5167//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-common.html
Findbugs warnings: https://builds.apache.org/job/PreCommit-HBASE-Build/5167//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-server.html
Findbugs warnings: https://builds.apache.org/job/PreCommit-HBASE-Build/5167//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-hadoop-compat.html
Console output: https://builds.apache.org/job/PreCommit-HBASE-Build/5167//console

This message is automatically generated.
                
> Move site back up out of hbase-assembly; bad idea
> -------------------------------------------------
>
>                 Key: HBASE-8286
>                 URL: https://issues.apache.org/jira/browse/HBASE-8286
>             Project: HBase
>          Issue Type: Task
>            Reporter: stack
>            Assignee: stack
>         Attachments: 8286.txt
>
>
> Redoing the packaging, I thought it smart putting it all under the new hbase-assembly
module.  A few weeks later, it is not looking like a good idea (Enis suggested moving the
site was maybe 'odd').  Here are a few issues:
> + The generated reports will have mention of hbase-assembly because that is where they
are being generated (Elliott pointed out the the scm links mention hbase-assembly instead
of trunk).
> + Doug Meil wants to build and deploy the site but currently deploy is a bit awkward
to explain because site presumes it is top level so staging goes to the wrong place and you
have to come along and do fixup afterward; it shouldn't be so hard.
> A possible downside is that we will break Nicks site check added to hadoopqa because
site is an aggregating build plugin... but lets see.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Mime
View raw message