Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[AUTOCUT] Gradle Check Failure. #6132

Closed
github-actions bot opened this issue Feb 1, 2023 · 5 comments
Closed

[AUTOCUT] Gradle Check Failure. #6132

github-actions bot opened this issue Feb 1, 2023 · 5 comments
Labels
bug Something isn't working CI CI related flaky-test Random test failure that succeeds on second run >test-failure Test failure from CI, local build, etc.

Comments

@github-actions
Copy link
Contributor

github-actions bot commented Feb 1, 2023

A gradle check workflow has failed after merge.

PR: https://build.ci.opensearch.org/job/gradle-check/10397/
CommitId: 6176ddc

@github-actions github-actions bot added >test-failure Test failure from CI, local build, etc. bug Something isn't working labels Feb 1, 2023
@saratvemulapalli
Copy link
Member

> Task :plugins:analysis-icu:test
org.gradle.internal.remote.internal.ConnectException: Could not connect to server [1a6c4fd3-2080-4d70-aadc-778fbf990c5e port:42123, 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.****/sun.nio.ch.Net.pollConnect(Native Method)
	at java.****/sun.nio.ch.Net.pollConnectNow(Net.java:672)
	at java.****/sun.nio.ch.SocketChannelImpl.finishTimedConnect(SocketChannelImpl.java:1191)
	at java.****/sun.nio.ch.SocketChannelImpl.blockingConnect(SocketChannelImpl.java:1233)
	at java.****/sun.nio.ch.SocketAdaptor.connect(SocketAdaptor.java:102)
	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

Looks unreleated to the changes.

@saratvemulapalli
Copy link
Member

Subsequent commits are passing, closing this!

@peternied peternied reopened this May 3, 2023
@peternied peternied added the flaky-test Random test failure that succeeds on second run label May 3, 2023
@peternied
Copy link
Member

New reproduction of the failure https://build.ci.opensearch.org/job/gradle-check/14816/consoleFull

* What went wrong:
Execution failed for task ':modules:analysis-common:test'.
> Process 'Gradle Test Executor 587' finished with non-zero exit value 1
  This problem might be caused by incorrect test process configuration.
  Please refer to the test execution section in the User Manual at https://docs.gradle.org/8.1.1/userguide/java_testing.html#sec:test_execution
org.gradle.internal.remote.internal.ConnectException: Could not connect to server [304ccce8-64cf-4a10-93d3-4a8ccc2aafc7 port:45325, 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.****/sun.nio.ch.Net.pollConnect(Native Method)
	at java.****/sun.nio.ch.Net.pollConnectNow(Net.java:672)
	at java.****/sun.nio.ch.SocketChannelImpl.finishTimedConnect(SocketChannelImpl.java:1141)
	at java.****/sun.nio.ch.SocketChannelImpl.blockingConnect(SocketChannelImpl.java:1183)
	at java.****/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

@peternied
Copy link
Member

We did some more experiments and it seems to be somewhat related to the maxParallelForks.
The machines in the cluster have 72 cores, so by default Gradle should spin up 72 JVMs to run the tests. If we reduce it to 8, we don’t see those connection errors. With 12 it sometimes works, sometimes not. Does Gradle have some issues with a “larger” amount of forks maybe?

https://discuss.gradle.org/t/connectexception-could-not-connect-to-server-when-using-gradlew-test-together-with-slurm/10254/3

Maybe we are hitting a usable limit on network connections?

@dblock
Copy link
Member

dblock commented Jul 19, 2023

Old, Passing on 1d3b006

@dblock dblock closed this as completed Jul 19, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working CI CI related flaky-test Random test failure that succeeds on second run >test-failure Test failure from CI, local build, etc.
Projects
None yet
Development

No branches or pull requests

3 participants