slachiewicz opened a new pull request, #2270: URL: https://github.com/apache/maven-resolver/pull/2270
`JettyTransporterTest.testGet_HTTP3` still fails on `windows-latest` with "Failed to find a port free for both TCP and UDP" after #2150 raised the retries from 20 to 100 (latest: [job 127729314994](https://github.com/apache/maven-resolver/actions/runs/42168114705/job/127729314994)). The retries are not independent on Windows: the probe takes OS-assigned ephemeral TCP ports, which Windows hands out in sequence, and Hyper-V reserves UDP port blocks 100 ports wide on the runner, so a probe that starts inside a reserved UDP block walks through all of it and gives up. The TCP and UDP exclusion ranges differ, which is why the TCP side never objects. The probe now draws random candidates below the Linux and Windows ephemeral ranges and binds TCP and UDP together on each candidate, so one reserved block cannot consume the whole retry budget. The HTTP/2 and HTTP/3 connectors still share one port number, as the Jetty client registers both transports on a single origin. Verified: `mvn -pl maven-resolver-transport-jetty -am -Dtest='JettyTransporterTest#testGet_HTTP3*' test` on JDK 21 (macOS) → `testGet_HTTP3` and `testGet_HTTP3Only` pass. Not run on Windows locally; the `windows-latest` job of this PR is the check that matters. --- - [x] I hereby declare this contribution to be licensed under the [Apache License Version 2.0, January 2004](https://www.apache.org/licenses/LICENSE-2.0) -- 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]
