Nick Dimiduk created HBASE-25156:
------------------------------------
Summary: TestMasterFailover.testSimpleMasterFailover is flaky
Key: HBASE-25156
URL: https://issues.apache.org/jira/browse/HBASE-25156
Project: HBase
Issue Type: Test
Components: test
Affects Versions: 3.0.0-alpha-1
Reporter: Nick Dimiduk
{noformat}
[ERROR] Tests run: 2, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 32.996
s <<< FAILURE! - in org.apache.hadoop.hbase.master.TestMasterFailover
[ERROR]
org.apache.hadoop.hbase.master.TestMasterFailover.testSimpleMasterFailover
Time elapsed: 12.317 s <<< FAILURE!
java.lang.AssertionError: expected:<1> but was:<2>
at
org.apache.hadoop.hbase.master.TestMasterFailover.testSimpleMasterFailover(TestMasterFailover.java:133)
{noformat}
Looks like this test depends on metrics to be updated as a source of
side-effect used to verify the test. Seems like it should retry the check a few
times, or maybe we need a last-updated monotonic value that the test can check
before and after it expects a change to be visible.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
