hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hudson (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-14930) check_compatibility.sh needs smarter exit codes
Date Sat, 05 Dec 2015 06:17:11 GMT

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

Hudson commented on HBASE-14930:
--------------------------------

FAILURE: Integrated in HBase-1.3-IT #357 (See [https://builds.apache.org/job/HBase-1.3-IT/357/])
HBASE-14930 check_compatibility.sh needs smarter exit codes (apurtell: rev 9bf4777af5645f81737acb2b507425a728e7cb85)
* dev-support/check_compatibility.sh


> check_compatibility.sh needs smarter exit codes
> -----------------------------------------------
>
>                 Key: HBASE-14930
>                 URL: https://issues.apache.org/jira/browse/HBASE-14930
>             Project: HBase
>          Issue Type: Bug
>            Reporter: Dima Spivak
>            Assignee: Dima Spivak
>             Fix For: 2.0.0, 1.2.0, 1.3.0, 1.1.3, 0.98.17, 1.0.4
>
>         Attachments: HBASE-14930_master_v1.patch
>
>
> The check_compatibility.sh tool in dev_support uses the Java API Compliance Checker to
do static analysis of source/binary incompatibilties between two HBase branches. One problem,
though, is that the script has a few instances where it may return an exit code of 1 (e.g.
if Maven steps fail), but this is the same exit code that the Java ACC tool itself uses to
denote that the tool succeeded, but found incompatibilities.



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

Mime
View raw message