You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@calcite.apache.org by "Ran Tao (Jira)" <ji...@apache.org> on 2023/08/02 07:13:00 UTC
[jira] [Commented] (CALCITE-5886) Task :spark:testClasses unstable due to ConnectException
[ https://issues.apache.org/jira/browse/CALCITE-5886?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17750151#comment-17750151 ]
Ran Tao commented on CALCITE-5886:
----------------------------------
[~shenlang] hi, Shen. Some occasional CI failures are unavoidable.
I think you can make an empty commit or re-squash your commit to trigger CI workflow again.
details you can refer [https://calcite.apache.org/develop/] and use the way below:
In the special case, that the CI build failed, and the failure is not caused by your changes create an empty commit (git commit --allow-empty) and push it.
> Task :spark:testClasses unstable due to ConnectException
> ---------------------------------------------------------
>
> Key: CALCITE-5886
> URL: https://issues.apache.org/jira/browse/CALCITE-5886
> Project: Calcite
> Issue Type: Improvement
> Components: spark
> Affects Versions: 1.35.0
> Reporter: LakeShen
> Priority: Major
>
> After I pushed my pr,I saw the calcite CI/CD workflow has the following error:
> {code:java}
> > Task :spark:testClasses
> Unexpected exception thrown.
> org.gradle.internal.remote.internal.MessageIOException: Could not read message from '/127.0.0.1:60778'.
> at org.gradle.internal.remote.internal.inet.SocketConnection.receive(SocketConnection.java:94)
> at org.gradle.internal.remote.internal.hub.MessageHub$ConnectionReceive.run(MessageHub.java:270)
> at org.gradle.internal.concurrent.ExecutorPolicy$CatchAndRecordFailures.onExecute(ExecutorPolicy.java:64)
> at org.gradle.internal.concurrent.ManagedExecutorImpl$1.run(ManagedExecutorImpl.java:49)
> at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1136)
> at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:635)
> at java.base/java.lang.Thread.run(Thread.java:833)
> Caused by: java.lang.IllegalArgumentException
> at org.gradle.internal.remote.internal.hub.InterHubMessageSerializer$MessageReader.read(InterHubMessageSerializer.java:72)
> at org.gradle.internal.remote.internal.hub.InterHubMessageSerializer$MessageReader.read(InterHubMessageSerializer.java:52)
> at org.gradle.internal.remote.internal.inet.SocketConnection.receive(SocketConnection.java:81)
> ... 6 more
> > Task :spark:test FAILED
> org.gradle.internal.remote.internal.ConnectException: Could not connect to server [8185c6ce-e464-4551-8250-0adaec77721f port:34907, addresses:[/127.0.0.1]]. Tried addresses: [/127.0.0.1].
> at org.gradle.internal.remote.internal.inet.TcpOutgoingConnector.connect(TcpOutgoingConnector.java:67)
> at org.gradle.internal.remote.internal.hub.MessageHubBackedClient.getConnection(MessageHubBackedClient.java:36)
> at org.gradle.process.internal.worker.child.SystemApplicationClassLoaderWorker.call(SystemApplicationClassLoaderWorker.java:103)
> at org.gradle.process.internal.worker.child.SystemApplicationClassLoaderWorker.call(SystemApplicationClassLoaderWorker.java:65)
> at worker.org.gradle.process.internal.worker.GradleWorkerMain.run(GradleWorkerMain.java:69)
> at worker.org.gradle.process.internal.worker.GradleWorkerMain.main(GradleWorkerMain.java:74)
> Caused by: java.net.ConnectException: Connection refused
> at java.base/sun.nio.ch.Net.pollConnect(Native Method)
> at java.base/sun.nio.ch.Net.pollConnectNow(Net.java:672)
> at java.base/sun.nio.ch.SocketChannelImpl.finishTimedConnect(SocketChannelImpl.java:1141)
> at java.base/sun.nio.ch.SocketChannelImpl.blockingConnect(SocketChannelImpl.java:1183)
> at java.base/sun.nio.ch.SocketAdaptor.connect(SocketAdaptor.java:98)
> at org.gradle.internal.remote.internal.inet.TcpOutgoingConnector.tryConnect(TcpOutgoingConnector.java:81)
> at org.gradle.internal.remote.internal.inet.TcpOutgoingConnector.connect(TcpOutgoingConnector.java:54)
> ... 5 more {code}
> It looks like the network issue caused this problem.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)