fuyou001 opened a new issue, #10822: URL: https://github.com/apache/rocketmq/issues/10822
### Before Creating the Bug Report - [x] I found a bug, not just asking a question, which should be created in GitHub Discussions. - [x] I have searched the GitHub Issues and GitHub Discussions of this repository and believe that this is not a duplicate. - [x] I have confirmed that this bug belongs to the current repository, not other repositories of RocketMQ. ### Runtime platform environment GitHub Actions `ubuntu-latest`, running the `Build and Run Tests by Bazel` workflow with Bazel remote execution. ### RocketMQ version - Branch: `develop` - Observed workflow run: https://github.com/apache/rocketmq/actions/runs/31065433437/job/92502049511 ### JDK Version Bazel-managed Java test runtime; the workflow does not explicitly pin a JDK version. ### Describe the Bug `//broker:src/test/java/org/apache/rocketmq/broker/BrokerShutdownTest` inherits the default Bazel `small` test size from `GenTestRules`, which gives the target a timeout of approximately 60 seconds. The test class contains four test methods, and every method constructs, initializes, starts, and shuts down a complete `BrokerController`. Broker shutdown serially stops Netty event executors, message-store services, POP services, timer services, and other background resources. The total runtime can therefore exceed the `small` timeout even when all shutdown operations behave normally. In the observed run, the target was terminated with `TIMEOUT` after 61.6 seconds while executing the fourth broker shutdown. The same timeout has also appeared on unrelated pull requests, indicating an existing test-size classification issue rather than a regression in the triggering pull request. ### Steps to Reproduce Run the Bazel broker shutdown test with the current generated rule: ```shell bazel test --config=remote //broker:src/test/java/org/apache/rocketmq/broker/BrokerShutdownTest ``` On a sufficiently loaded remote executor, the four complete broker lifecycle tests cumulatively exceed the `small` test timeout. ### What Did You Expect to See? The test should be assigned a timeout appropriate for its integration-style workload and complete without being terminated while broker shutdown is progressing normally. ### What Did You See Instead? Bazel terminates the target at approximately 60 seconds: ```text //broker:src/test/java/org/apache/rocketmq/broker/BrokerShutdownTest TIMEOUT in 61.6s ``` ### Additional Context Classifying `BrokerShutdownTest` in `medium_tests` changes the generated test rule to `size = "medium"`. This only adjusts the Bazel timeout classification; production code and test behavior remain unchanged. -- 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]
