This is consistent with what I’ve been experiencing. These issues do not happen all the time.
Thanks for getting the tests running again. How do I access this information normally without going through you? On Sat, May 9, 2020 at 1:32 AM Emmanuel Lécharny <[email protected]> wrote: > On 09/05/2020 01:04, Jonathan Valliere wrote: > > I tried 2.1.2 earlier and that was intermittently failing on one or > another > > SSL test also. I’m going to have to look at it again. Either a socket > bind > > test or ssl test fails or hangs randomly on my side. > > > FTR, the build with Java 11 hanged on the SSL test in the CI. > > > The java 14 build has also some error : > > [INFO] Running org.apache.mina.transport.socket.nio.SocketBindTest > > [ERROR] Tests run: 7, Failures: 0, Errors: 1, Skipped: 1, Time elapsed: > 2.605 s <<< FAILURE! - in > org.apache.mina.transport.socket.nio.SocketBindTest [ERROR] > testManyTimes(org.apache.mina.transport.socket.nio.SocketBindTest) Time > elapsed: 0.047 s <<< ERROR! java.io.IOException: Error while binding on > localhost/127.0.0.1:46531 > Caused by: java.net.BindException: Address already in use > > > This is not triggered when running the java 8 or 11 tests. > > > > > On Fri, May 8, 2020 at 6:31 PM Emmanuel Lécharny <[email protected]> > > wrote: > > > >> I'm also adding CI instances for Java 11 and 14, on both windows and > linux. > >> > >> On 09/05/2020 00:20, Emmanuel Lécharny wrote: > >>> FTR, the latest 2.1.X build was successful : > >>> > >>> > >>> > >> > https://builds.apache.org/view/M-R/view/MINA/job/MINA-2.1.X-jdk1.8-ubuntu/8/console > >>> > >>> > >>> On 09/05/2020 00:07, Emmanuel Lécharny wrote: > >>>> On 08/05/2020 18:39, Jonathan Valliere wrote: > >>>>> Do we have CI running for Mina on the primary branches? If so where > >>>>> is the > >>>>> daily reports? > >>>> We don't have daily builds, we have builds triggered on commits. Now, > >>>> the CI was badly configured, due to a change in the branches names : > >>>> it was expecting to build the 2.0 and 2.1 branches, which are now > >>>> named 2.0.X and 2.1.X. > >>>> > >>>> I have fixed that, the result should be sent to the [email protected] > >>>> mailing list shortly. > >>>> > >>>> > >> --------------------------------------------------------------------- > >> To unsubscribe, e-mail: [email protected] > >> For additional commands, e-mail: [email protected] > >> > >> > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > >
