Caideyipi opened a new pull request, #18904: URL: https://github.com/apache/iotdb/pull/18904
## Description `IoTDBPipeAutoDropIT.testAutoDropFinitePipesWithoutDataRegion` creates pipes that start automatically, then redundantly calls `startPipe` on them. With no DataRegions to process, the query/history-only pipes can finish and be auto-dropped before those calls run. The failure log shows the query pipe being removed before its start procedure validates it, returning `PIPE_ERROR` (1107) instead of the expected success (200). Remove the redundant starts and wait directly for the existing assertions: both finite pipes disappear while the realtime-only pipe remains. A comment explains the race. This keeps all create/show/drop status checks and the auto-drop assertions. ## Validation - `mvn spotless:apply -pl integration-test -P with-integration-tests` passed. - `git diff --check` passed. - Attempted the single method with the `MultiClusterIT2DualTreeAutoEnhanced` profile. The reactor did not reach IT execution because the local JVM exhausted Windows commit memory (OS error 1455), including with Maven capped at 2 GB. RAT and dependency analysis were skipped during the attempt due existing Go-client license-header findings and an unrelated `powermock-reflect` dependency finding in cached test classes. - A single-module `test-compile` attempt was blocked by the older installed Session artifact: unrelated `IoTDBSessionRelationalIT` calls `TableSessionBuilder.enableAutoCreateSchema(boolean)`, which that artifact does not provide. The target IT has not been executed locally. This PR has been self-reviewed. -- 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]
