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-12249) Script to help you adhere to the patch-naming guidelines
Date Tue, 14 Oct 2014 04:46:34 GMT

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

Hadoop QA commented on HBASE-12249:
-----------------------------------

{color:red}-1 overall{color}.  Here are the results of testing the latest attachment 
  http://issues.apache.org/jira/secure/attachment/12674668/HBASE-12249.patch
  against trunk revision .
  ATTACHMENT ID: 12674668

    {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 patch
that doesn't require tests.

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

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

    {color:red}-1 javadoc{color}.  The javadoc tool appears to have generated 1 warning messages.

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

    {color:red}-1 release audit{color}.  The applied patch generated 1 release audit warnings
(more than the trunk's current 0 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:green}+1 core tests{color}.  The patch passed unit tests in .

Test results: https://builds.apache.org/job/PreCommit-HBASE-Build/11334//testReport/
Release audit warnings: https://builds.apache.org/job/PreCommit-HBASE-Build/11334//artifact/trunk/patchprocess/patchReleaseAuditProblems.txt
Findbugs warnings: https://builds.apache.org/job/PreCommit-HBASE-Build/11334//artifact/patchprocess/newPatchFindbugsWarningshbase-client.html
Findbugs warnings: https://builds.apache.org/job/PreCommit-HBASE-Build/11334//artifact/patchprocess/newPatchFindbugsWarningshbase-annotations.html
Findbugs warnings: https://builds.apache.org/job/PreCommit-HBASE-Build/11334//artifact/patchprocess/newPatchFindbugsWarningshbase-thrift.html
Findbugs warnings: https://builds.apache.org/job/PreCommit-HBASE-Build/11334//artifact/patchprocess/newPatchFindbugsWarningshbase-server.html
Findbugs warnings: https://builds.apache.org/job/PreCommit-HBASE-Build/11334//artifact/patchprocess/newPatchFindbugsWarningshbase-hadoop2-compat.html
Findbugs warnings: https://builds.apache.org/job/PreCommit-HBASE-Build/11334//artifact/patchprocess/newPatchFindbugsWarningshbase-protocol.html
Findbugs warnings: https://builds.apache.org/job/PreCommit-HBASE-Build/11334//artifact/patchprocess/newPatchFindbugsWarningshbase-examples.html
Findbugs warnings: https://builds.apache.org/job/PreCommit-HBASE-Build/11334//artifact/patchprocess/newPatchFindbugsWarningshbase-hadoop-compat.html
Findbugs warnings: https://builds.apache.org/job/PreCommit-HBASE-Build/11334//artifact/patchprocess/newPatchFindbugsWarningshbase-prefix-tree.html
Findbugs warnings: https://builds.apache.org/job/PreCommit-HBASE-Build/11334//artifact/patchprocess/newPatchFindbugsWarningshbase-common.html
Findbugs warnings: https://builds.apache.org/job/PreCommit-HBASE-Build/11334//artifact/patchprocess/newPatchFindbugsWarningshbase-rest.html
Javadoc warnings: https://builds.apache.org/job/PreCommit-HBASE-Build/11334//artifact/patchprocess/patchJavadocWarnings.txt
Console output: https://builds.apache.org/job/PreCommit-HBASE-Build/11334//console

This message is automatically generated.

> Script to help you adhere to the patch-naming guidelines
> --------------------------------------------------------
>
>                 Key: HBASE-12249
>                 URL: https://issues.apache.org/jira/browse/HBASE-12249
>             Project: HBase
>          Issue Type: Improvement
>          Components: documentation, scripts
>            Reporter: Misty Stanley-Jones
>            Assignee: Misty Stanley-Jones
>            Priority: Minor
>         Attachments: HBASE-12249-v1.patch, HBASE-12249.patch
>
>
> I wrote a script to help me name patches correctly, and it may be helpful to others.
You use it from the branch where you are working, and it looks in your patches directory to
see if other versions of the patch exist, and appends -v<latest+1> if so. If you specify
-a, it creates an addendum patch, by appending -v<latest>-addendum. 
> In summary, it makes patches named like:
> HBASE-XXXX.patch
> HBASE-XXXX-vY.patch
> HBASE-XXXX-addendum.patch
> HBASE-XXXX-vY-addendum.patch
> The patch uses git format-patch if you have only one local commit, otherwise lets you
rebase or use git diff. It does not use --no-prefix.



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

Mime
View raw message