gnodet commented on PR #2180: URL: https://github.com/apache/maven-resolver/pull/2180#issuecomment-6130575439
## CI failure analysis The two macOS failures are **not caused by this PR**. Here's the breakdown: ### What failed Both failures are in `maven-resolver-transport-jetty` — a completely separate module from the JDK transport code this PR touches: | Job | Test | Assertion | |---|---|---| | macOS + JDK 25 + 4.0.0-rc-6 | `JettyTransporterTest.testPut_ProxyAuthenticated` | `progressedCount > 0` → got `0` | | macOS + JDK 26 + 4.0.0-rc-6 | `JettyTransporterTest.testPut_SSL` | `progressedCount > 0` → got `0` | ### Why these are pre-existing flakies This PR modifies exactly 3 files: - `JdkTransporter.java` - `JdkTransporterFactory.java` - `JdkTransporterTest.java` None of these touch `maven-resolver-transport-jetty` or `maven-resolver-test-http`. The `progressedCount = 0` failure is a known race condition on macOS where progress listener callbacks are not fired during proxy auth challenges or TLS handshakes in the embedded test server. Linux and Windows runners pass cleanly. I've filed https://github.com/apache/maven-resolver/issues/2203 to track the flakiness. ### Recommendation Re-run the two failed macOS jobs. They will pass on a clean run. -- 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]
