[HBASE-19803] False positive for the HBASE-Find-Flaky-Tests job

• Type: Sub-task
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 2.0.0-beta-2, 2.0.0
• Assignee: Unassigned
• Reporter: Duo Zhang
• Created: 16/Jan/18 13:42
• Updated: 21/Mar/18 22:23
• Resolved: 05/Feb/18 00:56

Description

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.

Issue Links

• relates to: HBASE-19862 Fix TestTokenAuthentication - fake RegionCoprocessorEnvironment is not of type HasRegionServerServices
• relates to: HBASE-19866 TestRegionServerReportForDuty doesn't timeout
• relates to: HBASE-19867 Split TestStochasticLoadBalancer into several small tests
• relates to: HBASE-19873 Add a CategoryBasedTimeout ClassRule for all UTs