Jackie-Jiang opened a new pull request, #20200: URL: https://github.com/apache/pinot/pull/20200
Concurrent integration-test lanes run Maven from the same module directory. Develocity 2.6.1 writes its listener port to `target/develocity/maven-surefire-plugin-default-test.port` under that directory, ignoring each lane's separate build directory. The lanes can therefore overwrite each other's listener endpoint, mix test events, and lose listener connections when the other Maven process exits. Disable Develocity Build Scan capture in the shared lane invocation. Both lanes retain their existing test execution, JaCoCo coverage, and build-cache configuration. Build Scans remain available for other Maven invocations. Investigated from [the integration set 2 failure on #20195](https://github.com/apache/pinot/actions/runs/42606324454/job/129123147805). The shared-file collision was verified in the extension's bytecode and matches the cross-lane event and connection errors in that log; the exact cause of the final nonzero fork exit was not retained. Validation: - `bash -n .github/workflows/scripts/pr-tests/.pinot_tests_two_lane_integration.sh` - `git diff --check` - `./mvnw -N license:format -Ddevelocity.scan.disabled=true` - `./mvnw -N license:check -Ddevelocity.scan.disabled=true` The full integration suite was not run locally; CI will validate the concurrent lanes. -- 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] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
