Skip to content

Failed to load eclipse jdt formatter: java.lang.RuntimeException: java.net.SocketTimeoutException: #100753

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

Closed
ChrisHegarty opened this issue Oct 12, 2023 · 3 comments · Fixed by #100789
Labels
:Delivery/Build Build or test infrastructure Team:Delivery Meta label for Delivery team

Comments

@ChrisHegarty
Copy link
Contributor

elastic / elasticsearch # main - packaging upgrade tests » 8.2.0,rocky-linux-8-packaging #1980
Failure message:
A problem occurred configuring project ':x-pack:plugin:esql:compute'.

java.io.IOException: Failed to load eclipse jdt formatter: java.lang.RuntimeException: java.net.SocketTimeoutException: timeout
Failed to load eclipse jdt formatter: java.lang.RuntimeException: java.net.SocketTimeoutException: timeout
> java.net.SocketTimeoutException: timeout
> timeout
> Socket closed

@ChrisHegarty ChrisHegarty added :Delivery/Build Build or test infrastructure Team:Delivery Meta label for Delivery team labels Oct 12, 2023
@elasticsearchmachine
Copy link
Collaborator

Pinging @elastic/es-delivery (Team:Delivery)

@ChrisHegarty
Copy link
Contributor Author

ChrisHegarty commented Oct 12, 2023

I'm not sure what the problem is here, but it look related to the machine environment or configuration?

I'm also not sure why it is failing on ':x-pack:plugin:esql:compute'. I don't see anything obvious in that gradle submodule.

More failures:

elastic / elasticsearch # main - packaging upgrade tests » 7.0.0,ubuntu-20.04-packaging #1980
Failure message:
A problem occurred configuring project ':x-pack:plugin:esql:compute'.

java.io.IOException: Failed to load eclipse jdt formatter: java.lang.RuntimeException: java.net.SocketTimeoutException: timeout
Failed to load eclipse jdt formatter: java.lang.RuntimeException: java.net.SocketTimeoutException: timeout
> java.net.SocketTimeoutException: timeout
> timeout

The following build resulted in FAILURE:
elastic / elasticsearch # main - packaging upgrade tests » 7.13.1,rocky-linux-8-packaging #1980
Failure message:
A problem occurred configuring project ':x-pack:plugin:esql:compute'.

java.io.IOException: Failed to load eclipse jdt formatter: java.lang.RuntimeException: java.net.SocketTimeoutException: timeout
Failed to load eclipse jdt formatter: java.lang.RuntimeException: java.net.SocketTimeoutException: timeout
> java.net.SocketTimeoutException: timeout
> timeout

The following build resulted in FAILURE:
elastic / elasticsearch # main - packaging upgrade tests » 8.8.2,rocky-linux-8-packaging #1980
Failure message:
A problem occurred configuring project ':x-pack:plugin:esql:compute'.

java.io.IOException: Failed to load eclipse jdt formatter: java.lang.RuntimeException: java.net.SocketTimeoutException: timeout
Failed to load eclipse jdt formatter: java.lang.RuntimeException: java.net.SocketTimeoutException: timeout
> java.net.SocketTimeoutException: timeout
> timeout

@mark-vieira
Copy link
Contributor

This was a fun one. It turns out the spotless tasks make queries to a public P2 repository to get dependency information and eagerly resolve those dependencies on task creation. We mostly avoid this problem by lazily registering and configuring these tasks but this project was configuring the spotlessJava task in a non-lazy way, triggering eager creation of the task, and therefore going out and fetching these dependencies on every build with an empty local cache. I've opened #100789 so that that we at least should never hit this error in a build that doesn't even run spotless.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
:Delivery/Build Build or test infrastructure Team:Delivery Meta label for Delivery team
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants