smengcl opened a new pull request, #11481: URL: https://github.com/apache/ozone/pull/11481
Generated-by: Claude Code (Opus 5.5) ## What changes were proposed in this pull request? Four unit test classes spend most of their time on waits or test data that no assertion depends on. Test only change, one commit per class. - `TestKeyValueContainer#testAutoCompactionSmallSstFile` creates 400 containers with 500 keys each and then sleeps 7s. Since HDDS-12233 container import no longer generates SST files, so the test only asserts that none exist. Create 10 containers per volume and drop the sleep. - `TestEventBufferOverflow` sleeps 2.1s between retry attempts. Advance a `MockClock` past the retry delay instead, as `TestReconTaskControllerImpl` already does. - `TestBlockInputStream` waits the default 1s `ozone.client.read.retry.interval` before each retry. Set the interval to 0, except in `testRefreshPipelineFunction`, which asserts the retry delay log. - `TestEventQueue` uses a handler that sleeps 2s for each of 11 events, processed by a single thread. Sleep 500ms instead. The test checks after 500ms that between 1 and 10 events are scheduled, and the 11th is scheduled only after about 5s. Test class time in CI, four recent master runs compared to a run of these changes on my fork: | Test class | master (s) | with change (s) | |---|---|---| | `TestKeyValueContainer` | 58 to 61 | 34.6 | | `TestEventBufferOverflow` | 39 | 10.7 | | `TestBlockInputStream` | 21 | 3.3 | | `TestEventQueue` | 23 | 6.2 | ## What is the link to the Apache JIRA https://issues.apache.org/jira/browse/HDDS-16933 ## How was this patch tested? - CI on my fork for the same changes on an earlier base (timings above): https://github.com/smengcl/hadoop-ozone/actions/runs/38185568538 - CI on my fork for this branch: https://github.com/smengcl/hadoop-ozone/actions/runs/ 🤖 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]
