315157973 opened a new pull request #9231: URL: https://github.com/apache/pulsar/pull/9231
### Motivation `CI-Unit-Brokers-Broker Group 1 / unit-tests` often executes for 120 minutes and then times out, and cause the CI queue to be blocked Take these CI records as an example: `https://github.com/apache/pulsar/pull/9206/checks?check_run_id=1719645381` `https://github.com/apache/pulsar/pull/9163/checks?check_run_id=1686466237` ... The running information will be printed when the unit test is executed, such as: `[INFO] Running org.apache.pulsar.broker.transaction.buffer.TransactionEntryImplTest` After execution, it will print: `[INFO] Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 2.453 s-in org.apache.pulsar.broker.transaction.buffer.TransactionEntryImplTest` Through script comparison, I found that `TransactionBufferClientTest`、`TransactionCoordinatorClientTest`.... has been executing for 120 minutes. If we directly add the suite-level timeout, it is not easy to find the problematic unit test. So I added a timeout to all transaction unit tests. ### Modifications add timeout ### Verifying this change ---------------------------------------------------------------- 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. For queries about this service, please contact Infrastructure at: [email protected]
