Thanks for taking a look at these. Ostensibly, Windows is failing because there is an System.exit() being called somewhere in the codepath of a SolrCLI test. We have a PR to address it, which should hopefully be merged relatively soon.
https://github.com/apache/solr/pull/3258 - Houston On Mon, Mar 24, 2025 at 10:12 AM Uwe Schindler <u...@thetaphi.de> wrote: > Hi, > > I can reproduce all failures on Windows. I can't run any :solr:core:test > on windows anymore, with neither JDK21 or any later version). I always > fails with exactly that message (just different port number): > > WARNING: Test org.apache.solr.TestRandomFaceting wrote 14,420,636 bytes > of output. > WARNING: Test org.apache.solr.schema.DocValuesTest wrote 11,400,417 > bytes of output. > WARNING: Test org.apache.solr.schema.TestCloudSchemaless wrote > 14,885,156 bytes of output. > > Unexpected exception thrown. > org.gradle.internal.remote.internal.MessageIOException: Could not write > '/127.0.0.1:53478'. > at > > org.gradle.internal.remote.internal.inet.SocketConnection.flush(SocketConnection.java:145) > at > > org.gradle.internal.remote.internal.hub.MessageHub$ConnectionDispatch.run(MessageHub.java:333) > at > > org.gradle.internal.concurrent.ExecutorPolicy$CatchAndRecordFailures.onExecute(ExecutorPolicy.java:64) > at > > org.gradle.internal.concurrent.AbstractManagedExecutor$1.run(AbstractManagedExecutor.java:48) > at > > java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1144) > at > > java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:642) > at java.base/java.lang.Thread.run(Thread.java:1583) > Caused by: java.io.IOException: Connection reset by peer > at java.base/sun.nio.ch.SocketDispatcher.write0(Native Method) > at > java.base/sun.nio.ch.SocketDispatcher.write(SocketDispatcher.java:54) > at > java.base/sun.nio.ch.IOUtil.writeFromNativeBuffer(IOUtil.java:137) > at java.base/sun.nio.ch.IOUtil.write(IOUtil.java:81) > at java.base/sun.nio.ch.IOUtil.write(IOUtil.java:58) > at > java.base/sun.nio.ch.SocketChannelImpl.write(SocketChannelImpl.java:542) > at > > org.gradle.internal.remote.internal.inet.SocketConnection$SocketOutputStream.writeWithNonBlockingRetry(SocketConnection.java:285) > at > > org.gradle.internal.remote.internal.inet.SocketConnection$SocketOutputStream.writeBufferToChannel(SocketConnection.java:272) > at > > org.gradle.internal.remote.internal.inet.SocketConnection$SocketOutputStream.flush(SocketConnection.java:266) > at > > org.gradle.internal.remote.internal.inet.SocketConnection.flush(SocketConnection.java:143) > ... 6 more > > > Task :solr:core:test > :solr:core:test (SUCCESS): 5018 test(s), 209 skipped > > It looks like somehow the connection between test runner and Gradle or > between Gradle Daemon stops. As this happens after a long time of > waiting, I have the feeling that some test is taking too long and then > the connection is reset. > > This is not an issue of JDK 24 or later, it is a general WIndows > problem. I am no longer possible to run the tests without that failure. > > Uwe > > Am 24.03.2025 um 13:32 schrieb Policeman Jenkins Server: > > Build: https://jenkins.thetaphi.de/job/Solr-main-Windows/5312/ > > Java: 64bit/hotspot/jdk-21.0.6 -XX:+UseCompressedOops -XX:+UseParallelGC > > > > All tests passed > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: builds-unsubscr...@solr.apache.org > > For additional commands, e-mail: builds-h...@solr.apache.org > > -- > Uwe Schindler > Achterdiek 19, D-28357 Bremen > https://www.thetaphi.de > eMail: u...@thetaphi.de > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: dev-unsubscr...@solr.apache.org > For additional commands, e-mail: dev-h...@solr.apache.org > >
