FrankChen021 opened a new issue, #20455: URL: https://github.com/apache/druid/issues/20455
_This issue was generated automatically by Claude Code (Anthropic's AI coding agent) running a scheduled CI-triage routine on behalf of @FrankChen021. Analysis and suggested fixes are AI-produced; please verify before acting on them._ **Status:** Open: no fix PR **Subject:** `AllocationMetricCollectorTest.testDelta` (processing, `unit tests (25, M*,A*,V*,W*)`) **Failures:** 1 · **First seen:** 2026-09-29 · **Last seen:** 2026-09-29 ### Root cause Line 61 asserts that the summed per-thread allocation delta exceeds `threads * 100000 * 16` bytes. The test assumes every `new Object()` in the worker loop is heap-allocated at 16 bytes. The list holding them is never read, so once the lambda is hot, C2 escape analysis can scalar-replace those allocations. The bound then fails, and it keeps failing on in-fork reruns because the code is already JIT-compiled. The failing commit (#20310) only changes `StringUtils` charset handling, and the test passed on the other six master runs that day, including the next commit. ### Suggested fix Make the allocations observable: publish each worker's list to a shared `volatile` field or collection, or allocate `byte[]` of known size and keep a reference. Also assert against a conservative fraction of the expected size rather than an exact lower bound. ### Occurrences Failed push-triggered master jobs only. The daily triage routine adds one row per new failed job. | Date | Commit | Job | Failure log | Detail | Reported in | |---|---|---|---|---|---| | 2026-09-29 | 3c3eec5b1c (#20310) | `unit tests (25, M*,A*,V*,W*)` | [job 109326225264](https://github.com/apache/druid/actions/runs/36544102361/job/109326225264) | line 61 `delta3 > generatedSize3` was false; 4/4 attempts | | -- 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]
