Caideyipi opened a new pull request, #18886: URL: https://github.com/apache/iotdb/pull/18886
## Description `PipeProcessorSubtaskWorkerTest.testOneHundredWaitingPipesDoNotWaitForWorkerPolling` can exhaust its 30-second timeout while a fresh Windows CI fork initializes Mockito/Byte Buddy, before any workers start. The [failing CI job](https://github.com/apache/iotdb/actions/runs/38682961547/job/116251377219) stops in Byte Buddy class loading and Mockito plugin initialization through `createRunnableSubtask:299`. Initialize a `PipeProcessorSubtask` mock in `@BeforeClass`, before JUnit starts either worker-notification test's timer. Both tests keep their existing deadlines, including the 5-second admission wake-up assertion. ## Validation - Clean reactor build and targeted tests: `mvn clean test -pl iotdb-core/datanode -am -Dtest=PipeProcessorSubtaskWorkerTest,PipeProcessorSubtaskExecutionGuardTest,PipeMemoryManagerTest -Dsurefire.failIfNoSpecifiedTests=false -DfailIfNoTests=false -Ddevelocity.off=true` — 18 tests passed. - `mvn spotless:apply -pl iotdb-core/datanode` — passed. - Injected a 35-second delay into the first Byte Buddy class load in separate JVMs: the original test reproduced the timeout at `createRunnableSubtask:299` after 30.0 seconds; the fixed test passed, with 37.3 seconds total including class setup. This PR has: - [x] been self-reviewed. - [x] added comments explaining the intent. - [x] modified existing tests to address the CI failure. -- 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]
