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?
What is the status of using java8 for IT tests? (current ITs are using a very very old version of Jetty 9.0.4...) On Mon, 19 Apr 2021 at 06:56, Tibor Digana <tibordig...@apache.org> wrote: > 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 <mthmuld...@apache.org> > wrote: > > > 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 have in common is > > that they all spin up an HTTP server during the test, but apparently > > that server cannot be reached under all circumstances. > > > > Does anyone have an idea what might be causing this and how we could > > address this? > > > > Thanks, > > > > Maarten > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org > > For additional commands, e-mail: dev-h...@maven.apache.org > > > > > -- Olivier Lamy http://twitter.com/olamy | http://linkedin.com/in/olamy
