smengcl opened a new pull request, #11470: URL: https://github.com/apache/ozone/pull/11470
Generated-by: Claude Code (Opus 5.5) ## What changes were proposed in this pull request? `TestCloseContainer#testCloseClosedContainer` intermittently fails with `expected: not equal but was: <0>` at the replica checksum assertion. The test waits until each datanode has the container CLOSED and has written the checksum file, then immediately asserts that every replica known to SCM has a non zero data checksum. `KeyValueHandler#closeContainer` marks the container CLOSED, then computes and persists the checksum, and only then sends the ICR carrying it. So the datanode side conditions can be met while that ICR is still in flight, and SCM still holds the replica from an earlier report with checksum 0. The fix waits for SCM to see non zero checksums for all replicas, using the same `GenericTestUtils.waitFor` check that HDDS-13346 added to `testContainerChecksumForClosedContainer` in the same class. ## What is the link to the Apache JIRA https://issues.apache.org/jira/browse/HDDS-16875 ## How was this patch tested? - `mvn -pl :ozone-integration-test -am test -Dtest=TestCloseContainer`: passed 3 of 3 runs locally. - The wait polls the condition the assertion checked, so it no longer depends on the ICR arriving before the assertion. - 10x10 [flaky-test-check](https://github.com/smengcl/hadoop-ozone/actions/runs/38103231876) on this branch: in progress 🤖 Generated with [Claude Code](https://claude.com/claude-code) -- 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]
