The other problem I saw that can lead to this error message is the JVM running out of memory. But I don’t know why either of these problems would have just started now. Here the discussions I found that look to concern the same issue:
[1] http://stackoverflow.com/questions/23523831/gradle-build-fail-process-gradle-test-executor-1-finished-with-non-zero-exit <http://stackoverflow.com/questions/23523831/gradle-build-fail-process-gradle-test-executor-1-finished-with-non-zero-exit> [2] https://discuss.gradle.org/t/strange-exception-thrown-running-unit-tests/2515/15 <https://discuss.gradle.org/t/strange-exception-thrown-running-unit-tests/2515/15> [3] https://discuss.gradle.org/t/unexpected-exception-thrown-org-gradle-messaging-remote-internal-messageioexception-could-not-read-message-from-0/1095 <https://discuss.gradle.org/t/unexpected-exception-thrown-org-gradle-messaging-remote-internal-messageioexception-could-not-read-message-from-0/1095> - Jared > On Dec 13, 2016, at 11:46 AM, Kirk Lund <kl...@pivotal.io> wrote: > > Ah, I only grepped for System.exit() but these all have an argument. Thanks! > > ChildVM, LocatorLauncherRemoteIntegrationTest, > ServerLauncherRemoteIntegrationTest are closing forked JVMs. > > CompiledClass, DistributedSystemConnectPerf, GemfireSequenceDisplay all have a > main with calls to exit. These wouldn't be invoked by a test. > > TestXACacheLoader, WANBootStrapping_Site1_Add, > WANBootStrapping_Site1_Remove, WANBootStrapping_Site2_Add, > WANBootStrapping_Site2_Remove all have a main as well but they appear to be > completed unused classes that can be deleted. > > There doesn't seem to be any JUnit tests that call exit except the launcher > tests. Also, I would expect to find a new test calling exit since this is a > new problem with our nightly build. > > > On Tue, Dec 13, 2016 at 11:35 AM, Jared Stewart <jstew...@pivotal.io> wrote: > >> These are all of the files I found within src/test: >> >> ChildVM.java >> CompiledClass.java >> DistributedSystemConnectPerf.java >> GemfireSequenceDisplay.java >> LocatorLauncherRemoteIntegrationTest.java >> ServerLauncherRemoteIntegrationTest.java >> TestXACacheLoader.java >> WANBootStrapping_Site1_Add.java >> WANBootStrapping_Site1_Remove.java >> WANBootStrapping_Site2_Add.java >> WANBootStrapping_Site2_Remove.java >> >>> On Dec 13, 2016, at 11:32 AM, Kirk Lund <kl...@pivotal.io> wrote: >>> >>> I tried grepping for "System.exit()" but the only java file I could find >> is >>> SystemAdmin.java which is an old command-line class. >>> >>> Which tests did you find calling exit? >>> >>> >>> On Tue, Dec 13, 2016 at 10:59 AM, Jared Stewart <jstew...@pivotal.io> >> wrote: >>> >>>> I did some poking around on Google and it looks like this exception can >> be >>>> thrown by Gradle when a test calls System.exit(). We do have some tests >>>> that call System.exit(), I wonder if one of them is at fault. >>>> >>>> - Jared >>>> >>>>> On Dec 13, 2016, at 9:36 AM, Kirk Lund <kl...@apache.org> wrote: >>>>> >>>>> I don't know what's causing these failures... looks like Gradle. Do we >>>> know >>>>> if the problem is Gradle or the Apache build machines? >>>>> >>>>> :geode-core:integrationTestUnexpected exception thrown. >>>>> org.gradle.internal.remote.internal.MessageIOException: Could not read >>>>> message from '/127.0.0.1:46897'. >>>>> at >>>>> org.gradle.internal.remote.internal.inet.SocketConnection.receive( >>>> SocketConnection.java:85) >>>>> at >>>>> org.gradle.internal.remote.internal.hub.MessageHub$ >>>> ConnectionReceive.run(MessageHub.java:250) >>>>> at >>>>> org.gradle.internal.concurrent.ExecutorPolicy$CatchAndRecordFailures. >>>> onExecute(ExecutorPolicy.java:54) >>>>> at >>>>> org.gradle.internal.concurrent.StoppableExecutorImpl$1.run( >>>> StoppableExecutorImpl.java:40) >>>>> at >>>>> java.util.concurrent.ThreadPoolExecutor.runWorker( >>>> ThreadPoolExecutor.java:1142) >>>>> at >>>>> java.util.concurrent.ThreadPoolExecutor$Worker.run( >>>> ThreadPoolExecutor.java:617) >>>>> at java.lang.Thread.run(Thread.java:745) >>>>> Caused by: java.lang.IllegalArgumentException >>>>> at >>>>> org.gradle.internal.remote.internal.hub.InterHubMessageSerializer$ >>>> MessageReader.read(InterHubMessageSerializer.java:71) >>>>> at >>>>> org.gradle.internal.remote.internal.hub.InterHubMessageSerializer$ >>>> MessageReader.read(InterHubMessageSerializer.java:52) >>>>> at >>>>> org.gradle.internal.remote.internal.inet.SocketConnection.receive( >>>> SocketConnection.java:78) >>>>> ... 6 more >>>>> org.gradle.internal.remote.internal.ConnectException: Could not >> connect >>>> to >>>>> server [324ba98c-8390-4910-98fc-0ba81e170929 port:49771, >>>>> addresses:[/0:0:0:0:0:0:0:1, /127.0.0.1]]. Tried addresses: >>>>> [/0:0:0:0:0:0:0:1, /127.0.0.1]. >>>>> at >>>>> org.gradle.internal.remote.internal.inet.TcpOutgoingConnector.connect( >>>> TcpOutgoingConnector.java:66) >>>>> at >>>>> org.gradle.internal.remote.internal.hub.MessageHubBackedClient. >>>> getConnection(MessageHubBackedClient.java:35) >>>>> at >>>>> org.gradle.process.internal.worker.child. >> SystemApplicationClassLoaderWo >>>> rker.call(SystemApplicationClassLoaderWorker.java:71) >>>>> at >>>>> org.gradle.process.internal.worker.child. >> SystemApplicationClassLoaderWo >>>> rker.call(SystemApplicationClassLoaderWorker.java:45) >>>>> at >>>>> worker.org.gradle.process.internal.worker.GradleWorkerMain.run( >>>> GradleWorkerMain.java:61) >>>>> at >>>>> worker.org.gradle.process.internal.worker.GradleWorkerMain.main( >>>> GradleWorkerMain.java:66) >>>>> Caused by: java.net.ConnectException: Connection refused >>>>> at sun.nio.ch.SocketChannelImpl.checkConnect(Native Method) >>>>> at sun.nio.ch.SocketChannelImpl.finishConnect( >>>> SocketChannelImpl.java:717) >>>>> at sun.nio.ch.SocketAdaptor.connect(SocketAdaptor.java:111) >>>>> at >>>>> org.gradle.internal.remote.internal.inet.TcpOutgoingConnector. >>>> tryConnect(TcpOutgoingConnector.java:80) >>>>> at >>>>> org.gradle.internal.remote.internal.inet.TcpOutgoingConnector.connect( >>>> TcpOutgoingConnector.java:53) >>>>> ... 5 more >>>>> FAILED >>>> >>>> >> >>
