lhotari opened a new issue, #24856: URL: https://github.com/apache/pulsar/issues/24856
### Search before reporting - [x] I searched in the [issues](https://github.com/apache/pulsar/issues) and found nothing similar. ### Motivation Currently Broker Group 1 takes about 40 to 45 minutes to run. Group 4 takes less than 15 minutes. It would be useful to move tests from Group 1 to Group 4 so that the duration of the jobs would be more balanced. ### Solution Create a new TestNG group called "broker-4" (it's just a string that is assigned as the group value for Test annotations) and selecting the tests based on the assigned group. The tests are run using https://github.com/apache/pulsar/blob/master/build/run_unit_group.sh script. There's a function for each group. It's possible to use diagnostics from Gradle Develocity about the test timings to move tests that take about 15 minutes to run from group 1 to group 4. Develocity: https://develocity.apache.org/scans?search.rootProjectNames=Pulsar The easiest way to find the correct Develocity build job is to go to https://github.com/apache/pulsar/actions/workflows/pulsar-ci.yaml?query=branch%3Amaster and then click on the latest completed build for master branch, for example https://github.com/apache/pulsar/actions/runs/18496112335 and then find the link. <img width="848" height="487" alt="Image" src="https://github.com/user-attachments/assets/e709df8c-f208-4731-9455-9311c7fdda11"; /> It's the first link. For example, in this case, it takes to https://develocity.apache.org/s/zvacriinkax24 . Tests can be analysed in the "Tests" section, for example https://develocity.apache.org/s/zvacriinkax24/tests/overview Moving the replicator related tests from broker group is most likely sufficient. In that case, it makes sense to call the group name "replication" instead of "broker-4". ### Alternatives _No response_ ### Anything else? _No response_ ### Are you willing to submit a PR? - [ ] I'm willing to submit a PR! -- 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]
