ai-yang commented on PR #10759: URL: https://github.com/apache/rocketmq/pull/10759#issuecomment-5634248224
New-head CI triage for `f9247d2a6`: - Bazel run https://github.com/apache/rocketmq/actions/runs/34596301031 completed 595 test targets: 594 passed, with only `PopPriorityIT` failing. - The downloaded `bazel-test-results` XML identifies `test_priority_consume_always_high_priority[kv=false, ascending=true]`, line 131: expected priority `7`, received `6`. The other parameter combinations of this method passed. - The local CQ/Ext regression reactor passed 24/24. The same-base Bazel workflow for #10697 also passed: https://github.com/apache/rocketmq/actions/runs/34596300805. This points to the priority-consumption integration path, but it does not by itself establish a flaky test or exclude interaction with this change: the integration fixture enables ConsumeQueueExt. The full stdout was omitted from the job log because it exceeded the output-size limit, so the available XML only establishes the assertion above. I attempted to rerun the Bazel workflow, but GitHub rejected the author-side request with `run cannot be rerun`. Could a maintainer rerun this workflow on the same head? If the failure repeats, the next check should compare this exact priority case on the base and PR head before changing production code. The remaining CI jobs are still running. -- 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]
