Caideyipi opened a new pull request, #18938: URL: https://github.com/apache/iotdb/pull/18938
## Description The first cancellation cleanup test can exhaust its 15-second JUnit timeout while constructing `SeriesScanUtil`, before driver execution starts. This includes cold scanner and Mockito initialization in each fresh Surefire JVM, so a slow runner reports `TestTimedOut` at `newScanner:543` without reaching the cleanup assertions. Run the driver on a worker and apply the five-second deadline to its future instead of the entire test method. Preserve the expected failure identity, metadata-read count, resource-release assertions, and existing five-second notification waits. Shut down notifications gracefully after opening the driver-close latch so failure cleanup can finish without interruption. ## Validation - Injected a 17-second delay into `SeriesScanUtil.<clinit>`: the original test reproduces the reported method and `newScanner:543` timeout stack; the updated class passes all 33 parameterized cases under the same delay. - Compiled the changed test and related tests with `javac`, then ran Maven Surefire: 54 tests passed across `SeriesScanUtilCancellationTest`, `DataDriverTest`, `FragmentInstanceExecutionTest`, `FragmentInstanceStateMachineTest`, `FileReaderReferenceLifecycleTest`, and `RegionQueryInitializationLockTest`. - Repeated the updated cancellation test class 100 times: 3,300 cases passed. - `mvn -o -pl iotdb-core/datanode spotless:check` passed. This PR has: - [x] been self-reviewed. - [x] updated existing unit tests and comments explaining the timeout boundary. -- 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]
