-
Notifications
You must be signed in to change notification settings - Fork 659
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
Test sometimes fails on GH-Action Java 21 #3008
Comments
-1 means the server has gone away - no HTTP status code. #3006 may be related. i.e., it passed both build actions which currently seems to be only 50%. Rerunning a workflow step is usually successful - which does make much sense to me. I don't know whats happening - my (very wild) guess is that the server isn't GC-reachable and gets killed by a being GC-collected.
|
The same thing happen with java17 - less frequent. It is only two classes where it happens. I would be nervous of making it go away by creating a server per test because there is a root issue somewhere. |
Experiment: I added a static lock in There were 3 Java21 and 1 Java17 failures.
|
Version
main
What happened?
When I manually start github actions on linux it sometimes gives the following error:
Other times it passes.
Haven't seen it apply to the java 17 job.
To me it looks unrelated to the commits where it happens, e.g OyvindLGjesdal@8cf9c8b
Relevant output and stacktrace
Are you interested in making a pull request?
None
The text was updated successfully, but these errors were encountered: