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

Andrew Purtell edited comment on HBASE-18923 at 10/3/17 5:13 PM:
-----------------------------------------------------------------

Thanks. Bisect is not always reliable when dealing with flaky tests. I try to 
do one at the beginning of looking at a test failure anyway. Thanks for looking 
into this issue [~pankaj_kumar]. Would you like to provide a patch? The way the 
setup code in BeforeClass is waiting is not good for a couple of reasons and 
should be redone. Happy to assign it to you if you would like to take it. 
Please advise.


was (Author: apurtell):
Thanks. Bisect is not always reliable when dealing with flay tests. I try to do 
one at the beginning of looking at a test failure anyway. Thanks for looking 
into this issue [~pankaj_kumar]. Would you like to provide a patch? The way the 
setup code in BeforeClass is waiting is not good for a couple of reasons and 
should be redone. Happy to assign it to you if you would like to take it. 
Please advise.

> TestTableResource flaky on branch-1
> -----------------------------------
>
>                 Key: HBASE-18923
>                 URL: https://issues.apache.org/jira/browse/HBASE-18923
>             Project: HBase
>          Issue Type: Bug
>    Affects Versions: 1.4.0, 1.5.0
>            Reporter: Andrew Purtell
>
> Occasional NPE
> Flaked tests: 
> org.apache.hadoop.hbase.rest.TestTableResource.testTableInfoPB(org.apache.hadoop.hbase.rest.TestTableResource)
>   Run 1: TestTableResource.testTableInfoPB:271->checkTableInfo:184 NullPointer
>   Run 2: PASS
> org.apache.hadoop.hbase.rest.TestTableResource.testTableInfoXML(org.apache.hadoop.hbase.rest.TestTableResource)
>   Run 1: TestTableResource.testTableInfoXML:254->checkTableInfo:184 
> NullPointer
>   Run 2: PASS
> Tests run: 213, Failures: 0, Errors: 0, Skipped: 0, Flakes: 2



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

Reply via email to