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
HDDS-3013. Fix TestBlockOutputStreamWithFailures.java. #592
Conversation
@bshashikant there were various failures in 10 runs (at almost 10 minutes per run, this one cannot be run 20 times): https://github.com/adoroszlai/hadoop-ozone/runs/465142838
|
Thanks @adoroszlai . The fix was not complete as metric count validation checks post inducing failure were not removed from few tests. Latest patch addresses these. |
Thanks @bshashikant for updating the patch. There are still some failures:
|
Addressed failures. |
Thanks @bshashikant. Yet another one:
|
@bshashikant run with the latest update had 1 error:
|
@adoroszlai , can you please share log and output file for the failure? |
Sure, it's available in the https://github.com/adoroszlai/hadoop-ozone/suites/486485662/artifacts/2311772 |
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.
Thanks @bshashikant for the update, 10/10 tests passed with 78d0e6e.
|
What changes were proposed in this pull request?
Added configs for rpc and watch request timeout for ratis client and server. Modified the unit tests
to remove conditions for asserting on write chunk and putblock metric count in tests after inducing failure as given the nature of retry and async write along wit pipeline destruction, these counters cannot be deterministic after failure.
What is the link to the Apache JIRA
https://issues.apache.org/jira/browse/HDDS-3013
How was this patch tested?
Ran the unit test.