-
Notifications
You must be signed in to change notification settings - Fork 588
HDDS-3432. Enable TestBlockDeletion test cases. #1121
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
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.
|
|
Ran a workflow on the branch. |
c4149d7 to
c57686c
Compare
|
Thanks @lokeshj1703 for working on this. 3/20 runs failed with two different problems:
https://github.com/adoroszlai/hadoop-ozone/runs/808704334 |
|
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. |
|
Thanks @lokeshj1703 for updating the patch. 1/20 runs still failed with timeout: https://github.com/adoroszlai/hadoop-ozone/runs/814060939 |
|
@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. |
|
Thanks @lokeshj1703 for updating the patch. I still see 1/20 failure due to timeout at https://github.com/adoroszlai/hadoop-ozone/runs/844624809 |
|
@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. |
|
/pending "I still see 1/20 failure due to timeout at TestBlockDeletion.testBlockDeletion(TestBlockDeletion.java:174)." |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Marking this issue as un-mergeable as requested.
Please use /ready comment when it's resolved.
"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