Re: Failing IT's on Linux in GitHub Actions

yup definitely use loopback address (hostnames are not very reliable on such ephemeral nodes environments) On Mon, 19 Apr 2021 at 18:15, Tibor Digana wrote: > I had this problem with GH CI: > > java.net.BindException: Cannot assign requested address > at sun.nio.ch.Net.bind0(Native Method) > at

Re: Failing IT's on Linux in GitHub Actions

I had this problem with GH CI: java.net.BindException: Cannot assign requested address at sun.nio.ch.Net.bind0(Native Method) at sun.nio.ch.Net.bind(Net.java:461) at sun.nio.ch.Net.bind(Net.java:453) at sun.nio.ch.AsynchronousServerSocketChannelImpl.bind(AsynchronousServerSocketChannelImpl.java:16

Re: Failing IT's on Linux in GitHub Actions

Port 0 does not exist, only in your code. 0 means that a new unused local port is allocated. Again you have to use local loopback 127.0.0.1 as me. I had the same problem and I solved it. T On Mon, Apr 19, 2021 at 8:41 AM Maarten Mulders wrote: > All of those tests seem to follow the process of s

Re: Failing IT's on Linux in GitHub Actions

Hi Should we set java.net.preferIPv4Stack=true? Romain Manni-Bucau @rmannibucau | Blog | Old Blog | Github | LinkedIn

Re: Failing IT's on Linux in GitHub Actions

All of those tests seem to follow the process of starting a server at port 0 indeed. Some tests even start two servers in one test: MavenITmng4991NonProxyHostsTest and MavenITmng2387InactiveProxyTest. And in all three scenarios they use `InetAddress.getLocalHost().getCanonicalHostName()` to loo

Re: Failing IT's on Linux in GitHub Actions

yes, there was one more issue with host. I also had to turn "localhost" to 127.0.0.1 in the socket. T On Sun, Apr 18, 2021 at 11:48 PM Olivier Lamy wrote: > Hi, > Do not change ports or use hard coded ports. > The current ITs are using port 0 which means Jetty will allocate a > random available

Re: Failing IT's on Linux in GitHub Actions

Hi, Do not change ports or use hard coded ports. The current ITs are using port 0 which means Jetty will allocate a random available port. There must be some problems with host lookup. In some environments (such as kubernetes) using localhost or 127.0.0.1 can be problematic. What is the error? Wha

Re: Failing IT's on Linux in GitHub Actions

I had exactly the same problem and I added one more step to the CI which checked all open ports. For instance they changed something in Github and 8081 or 8082 was allocated. There was a conflict with the ports and I had to shift mine, that;s it. T On Sun, Apr 18, 2021 at 8:17 PM Maarten Mulders

Failing IT's on Linux in GitHub Actions

Hi all, It seems the following IT's predictably fail on Linux (not on Windows or MacOS) in GitHub Actions, but not at all in Jenkins: * MavenIT0146InstallerSnapshotNaming * MavenITmng2387InactiveProxyTest * MavenITmng4991NonProxyHostsTest This is also the case in master, by the way. What they