[
https://issues.apache.org/jira/browse/HBASE-21416?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
stack updated HBASE-21416:
--------------------------
Resolution: Fixed
Hadoop Flags: Reviewed
Fix Version/s: 2.3.0
3.0.0
Status: Resolved (was: Patch Available)
Lets try it. Pushed to master and branch-2. Thanks for the patch [~nkalmar] (I
removed change-id thingy before committing). Shout if you want it to go back to
other branches especially if you see it flakey on old branches still).
> Intermittent TestRegionInfoDisplay failure due to shift in relTime of
> RegionState#toDescriptiveString
> -----------------------------------------------------------------------------------------------------
>
> Key: HBASE-21416
> URL: https://issues.apache.org/jira/browse/HBASE-21416
> Project: HBase
> Issue Type: Test
> Reporter: Ted Yu
> Assignee: Norbert Kalmar
> Priority: Minor
> Fix For: 3.0.0, 2.3.0
>
> Attachments: HBASE-21416.master.001.patch
>
>
> Over
> https://builds.apache.org/job/HBase-Flaky-Tests/job/branch-2.1/1799/testReport/junit/org.apache.hadoop.hbase.client/TestRegionInfoDisplay/testRegionDetailsForDisplay/
> :
> {code}
> org.junit.ComparisonFailure: expected:<...:30 UTC 2018 (PT0.00[6]S ago),
> server=null> but was:<...:30 UTC 2018 (PT0.00[7]S ago), server=null>
> at
> org.apache.hadoop.hbase.client.TestRegionInfoDisplay.testRegionDetailsForDisplay(TestRegionInfoDisplay.java:78)
> {code}
> Here is how toDescriptiveString composes relTime:
> {code}
> long relTime = System.currentTimeMillis() - stamp;
> {code}
> In the test, state.toDescriptiveString() is called twice for the assertion
> where different return values from System.currentTimeMillis() caused the
> assertion to fail in the above occasion.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
