Details
-
Bug
-
Status: Resolved
-
Minor
-
Resolution: Cannot Reproduce
-
2.4.9
-
None
-
None
Description
There was an earlier issue where the problem was diagnosed as a race (see HBASE-20822). The test is flaky again now on MacOS aarch64, which is likely a timing/race issue again. The underlying hardware memory model is different so the JVM will be using memory barriers in more places on aarch64 than x86_64 etc. and multithreaded timings and interactions can be expected to be slightly different.
org.apache.hadoop.hbase.client.TestAsyncNonMetaRegionLocator.testMultiRegionTable[1]
[ERROR] Run 1: TestAsyncNonMetaRegionLocator.testMultiRegionTable:251->lambda$testMultiRegionTable$5:251->lambda$null$4:253->assertLocEquals:196 array lengths differed, expected.length=3 actual.length=0; arrays first differed at element [0]; expected:<49> but was:<end of array>
[INFO] Run 2: PASS
org.apache.hadoop.hbase.client.TestAsyncNonMetaRegionLocator.testRegionMove[1]
[ERROR] Run 1: TestAsyncNonMetaRegionLocator.testRegionMove:292->assertLocEquals:197 expected:<192.168.1.25,64070,1639793242964> but was:<192.168.1.25,64053,1639793242927>
[INFO] Run 2: PASS
org.apache.hadoop.hbase.client.TestAsyncNonMetaRegionLocator.testRegionReplicas[1]
[ERROR] Run 1: TestAsyncNonMetaRegionLocator.testRegionReplicas:433 expected:<3> but was:<1>
[INFO] Run 2: PASS
org.apache.hadoop.hbase.client.TestAsyncNonMetaRegionLocator.testReload[1]
[ERROR] Run 1: TestAsyncNonMetaRegionLocator.testReload:365->assertLocEquals:197 expected:<192.168.1.25,64083,1639793243015> but was:<192.168.1.25,64053,1639793242927>
[INFO] Run 2: PASS
org.apache.hadoop.hbase.client.TestAsyncNonMetaRegionLocator.testSingleRegionTable[1]
[ERROR] Run 1: TestAsyncNonMetaRegionLocator.testSingleRegionTable:205->assertLocEquals:197 expected:<192.168.1.25,64070,1639793242964> but was:<192.168.1.25,64053,1639793242927>
[INFO] Run 2: PASS
Attachments
Issue Links
- relates to
-
-
- Resolved
-