[
https://issues.apache.org/jira/browse/HBASE-19803?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16327526#comment-16327526
]
Appy commented on HBASE-19803:
------------------------------
bq. 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.
Makes sense.
This one suggests that it can be memory issue :
https://stackoverflow.com/questions/42298883/maven-build-failure-when-running-tests-due-to-jvm-crash
Looking at old nighly job
(https://builds.apache.org/job/HBase-Trunk_matrix/configure), it was using
-Xmx6100M. But the new jobs seem to be using just 3g
(https://github.com/apache/hbase/blob/master/dev-support/docker/Dockerfile#L40)
> 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)
