hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Appy (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-19803) False positive for the HBASE-Find-Flaky-Tests job
Date Wed, 24 Jan 2018 23:40:00 GMT

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

Appy commented on HBASE-19803:
------------------------------

bq. Notice here I only log the exception without throwing it out if it is called from the
surefire plugin. So it is killed by the surefire plugin? And then surefire plugin tells us
the VM exited abnormally...
Didn't understand what you meant.

Another possible cause for this one, from reading around, is, failed native call. That can
happen for so many reasons - over memory (but i think that one shows up explicitly as OOM),
apache machine killing jvm for overuse of resources? (wild guess), etc.
I think we really need hs_err files to help debug this one.


> False positive for the HBASE-Find-Flaky-Tests job
> -------------------------------------------------
>
>                 Key: HBASE-19803
>                 URL: https://issues.apache.org/jira/browse/HBASE-19803
>             Project: HBase
>          Issue Type: Bug
>            Reporter: Duo Zhang
>            Priority: Major
>
> It reports two hangs for TestAsyncTableGetMultiThreaded, but I checked the surefire output
> https://builds.apache.org/job/HBASE-Flaky-Tests/24830/artifact/hbase-server/target/surefire-reports/org.apache.hadoop.hbase.client.TestAsyncTableGetMultiThreaded-output.txt
> This one was likely to be killed in the middle of the run within 20 seconds.
> https://builds.apache.org/job/HBASE-Flaky-Tests/24852/artifact/hbase-server/target/surefire-reports/org.apache.hadoop.hbase.client.TestAsyncTableGetMultiThreaded-output.txt
> This one was also killed within about 1 minutes.
> The test is declared as LargeTests so the time limit should be 10 minutes. It seems that
the jvm may crash during the mvn test run and then we will kill all the running tests and
then we may mark some of them as hang which leads to the false positive.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Mime
View raw message