anmolnar opened a new pull request, #5592:
URL: https://github.com/apache/hbase/pull/5592
This is not included in Flaky Test reports, but happens quite frequently for
me locally. `testRecover()` passes the expected failure and throws error:
```
java.lang.AssertionError: flush should fail
at org.junit.Assert.fail(Assert.java:89)
at
org.apache.hadoop.hbase.io.asyncfs.TestFanOutOneBlockAsyncDFSOutput.testRecover(TestFanOutOneBlockAsyncDFSOutput.java:154)
```
Looks like it happens only if the other test `testConnectToDatanodeFailed()`
precedes it. They do similar thing: restart one of the DataNodes to generate
failure in FS connection. I've tried the following things to fix it:
- changed the ID of DataNode to be restarted to be unique in the 2 tests,
- added `CLUSTER.waitDatanodeFullyStarted()` at the end of
testConnectToDatanodeFailed.
None of them helped unfortunately, so I ended up with this ugly solution of
strict test ordering. Open for any ideas from experts.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
