chihsuan opened a new pull request, #10600: URL: https://github.com/apache/ozone/pull/10600
## What changes were proposed in this pull request? Test-only change. **Problem.** `TestOzoneDebugShell.testChunkInfoVerifyPathsAreDifferent` intermittently failed with `expected: <3> but was: <2>`. A RATIS THREE write is acknowledged on a Ratis majority, so right after the key is written one replica may not have applied the write yet. When `ozone debug replicas chunk-info` runs in that window, `ReadContainer` on the lagging datanode fails, the datanode is dropped from the response, and the test sees only 2 distinct block file paths instead of 3. **Fix.** Wait until all three datanodes report the block (three distinct paths) before asserting, using `GenericTestUtils.waitFor`, instead of asserting on a single read taken immediately after the write. A persistent error or an unexpected path count is reported via the wait's last observed state, so genuine regressions still surface with context rather than an opaque timeout. ## What is the link to the Apache JIRA https://issues.apache.org/jira/browse/HDDS-13434 ## How was this patch tested? - Ran the previously-flaky test locally; passes for all `BucketLayout` values. - Confirmed the wait is not vacuous: with the target temporarily set to an unreachable path count, the test times out as expected, proving the wait actually gates the assertion. - `flaky-test-check` on the fork, `TestOzoneIntegrationNonHA` `ALL`, 10x10: the `OzoneDebugShell` cases (including this test) passed in all 100 iterations. https://github.com/chihsuan/ozone/actions/runs/28101143264 - One unrelated pre-existing flake in `TestListKeysWithFSO` (`BUCKET_ALREADY_EXISTS` in test setup) appeared in a single split; it is not touched by this change. -- 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] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
