Uh oh!
There was an error while loading. Please reload this page.
HDDS-3432. Enable TestBlockDeletion test cases. - #1121
Conversation
codecov-commenter
commented
Jun 24, 2020
Codecov Report
@@ Coverage Diff @@## master #1121 +/- ##
============================================
- Coverage 70.56% 70.55% -0.02% - Complexity 9427 9437 +10
============================================
Files 965 967 +2 Lines 49063 49260 +197 Branches 4803 4825 +22 ============================================
+ Hits 34620 34754 +134 - Misses 12137 12184 +47 - Partials 2306 2322 +16 Continue to review full report at Codecov.
|
lokeshj1703
commented
Jun 25, 2020
Ran a workflow on the branch. |
c4149d7 to
c57686cCompareadoroszlai
commented
Jun 26, 2020
Thanks @lokeshj1703 for working on this. 3/20 runs failed with two different problems:
|
lokeshj1703
commented
Jun 26, 2020
Thanks @adoroszlai for verifying! I have pushed a commit which fixes the timeout issue. For the time being I have ignored the verifyPendingDeleteEvent check. I will need to think of another way for that test. FYI - I had enabled a workflow for this test at https://github.com/lokeshj1703/hadoop-ozone/actions?query=workflow%3ATestBlockDeletion2. I am not sure if it takes the latest changes from the branch though. |
adoroszlai
commented
Jun 27, 2020
Thanks @lokeshj1703 for updating the patch. 1/20 runs still failed with timeout: https://github.com/adoroszlai/hadoop-ozone/runs/814060939 |
lokeshj1703
commented
Jun 28, 2020
@adoroszlai Thanks for verifying! The test failed in the 20th iteration and it failed because of appendEntries timeout. |
@adoroszlai The workflow is now green. There were 2 failures in around 70 runs. One where cluster start timed out at waitForClusterToBeReady and another with appendEntriesTimeout. |
adoroszlai
commented
Jul 7, 2020
Thanks @lokeshj1703 for updating the patch. I still see 1/20 failure due to timeout at |
lokeshj1703
commented
Jul 7, 2020
@adoroszlai Thanks for verifying! I see appendEntries timeout in the particular run. The blocks creation in all the datanodes timed out in the run. The failure occurs in iteration 12. |
elek
commented
Aug 24, 2020
/pending "I still see 1/20 failure due to timeout at TestBlockDeletion.testBlockDeletion(TestBlockDeletion.java:174)." |
Thank you very much for the patch. I am closing this PR temporarily as there was no activity recently and it is waiting for response from its author. It doesn't mean that this PR is not important or ignored: feel free to reopen the PR at any time. It only means that attention of committers is not required. We prefer to keep the review queue clean. This ensures PRs in need of review are more visible, which results in faster feedback for all PRs. If you need ANY help to finish this PR, please contact the community on the mailing list or the slack channel." |
What changes were proposed in this pull request?
Enable block deletion test
What is the link to the Apache JIRA
https://issues.apache.org/jira/browse/HDDS-3432
How was this patch tested?
Enables a UT