RockteMQ-AI commented on issue #11085: URL: https://github.com/apache/rocketmq/issues/11085#issuecomment-5595154956
**Issue Evaluation** Category: `bug` | Status: **Confirmed** The reported test infrastructure issues have been verified against the current codebase (`develop@37808b38c`). **Root Cause (3 sub-issues):** 1. **`OffsetResetIT` scheduling race:** In `testResetOffsetSingleQueue()`, `hasConsumeBefore = listener.getMsgIndex().get()` is captured *after* sending reset requests. Replayed messages may already have arrived, inflating the baseline. The test then waits for `hasConsumeBefore + expectAfterReset` total messages — more than can actually be delivered, causing timeout. 2. **`OffsetResetForPopIT` leaked executors:** `testResetOffsetWhilePop()` and `testResetOffsetWhilePopOrderly()` create `Executors.newSingleThreadScheduledExecutor()` with 30-second loops that are never shut down. POP clients created directly by the test are not registered for cleanup, so background loops continue after assertions complete, producing excessive output. 3. **`enablePopBufferMerge` null-cache risk:** Tests enable `enablePopBufferMerge` after broker construction. If `PopConsumerService` was constructed without a cache, the revive logging path can dereference the absent cache (other POP operations already guard this case). **Impact:** Flaky CI, excessive test output (up to 1.52 GB), and potential NPE in revive path. **Severity:** medium — test infrastructure issue, no production data path affected, but blocks reliable CI. An automated fix proposal can be generated. Reply `/approve` to proceed with PR generation. --- *Automated evaluation by github-manager* -- 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]
