slachiewicz commented on PR #37: URL: https://github.com/apache/maven-executor/pull/37#issuecomment-5396124382
This bump is not the cause of its own red CI, and the run was cancelled rather than failed. `groovy-jsr223` appears only in the root `dependencyManagement`. No module declares it, so it reaches no classpath and `dependency:tree` never mentions it. Changing the managed version here cannot alter what is compiled or tested. What actually happened is that `EmbeddedMavenExecutorTest` hung, and the fail-fast job hit `ff-timeout-minutes: 15`. The same stall occurs on `main` without this bump, most recently in [run 30933906017](https://github.com/apache/maven-executor/actions/runs/30933906017), which stops at the identical point after the two preceding test classes pass with normal timings. It has taken down every fail-fast job that reached the test phase since 2026-08-09. Filed as #38 with the timings and the reason the existing `@Timeout(60)` does not catch it. #39 removes the managed entry, which was orphaned when `991f66f` deleted the `maven-batch-executor` module it was added for. Once that merges this PR becomes moot and Dependabot stops proposing bumps for an artifact the build does not use. Converting to draft rather than closing, so it stays visible until #39 lands. *This comment was created with AI assistance.* -- 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]
