-
Notifications
You must be signed in to change notification settings - Fork 24.9k
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
[CI] DedicatedClusterSnapshotRestoreIT#testMasterShutdownDuringFailedSnapshot Captured an uncaught exception ClosedByInterruptException #25062
Comments
That's because this is a JDK 9 build and those are JDK 9 flags and I suspect that you were not using JDK 9. |
Yep, that would most certainly be the case. Oops :) |
A reproducible failure on master:
This is not related to java 9, other similar failures: |
Another reproducible failure on 5.x (macOS):
Reproduce line:
|
Another one, still reproducible, @abeyad can you confirm that this is related to #24452 ?
|
@imotov and I debugged this issue - there are a couple things going on here for which I opened a new issue #25281 and silenced the test in 0c69734. I'm closing this issue as the problem has been identified and the new issue opened, and the AwaitsFix will be removed on the test once #25281 is resolved. |
https://elasticsearch-ci.elastic.co/job/elastic+elasticsearch+5.x+java9-periodic/2759/console
@abeyad Potentially related to #24452? Unsure, since I couldn't see the failure messages in that thread.
Couldn't reproduce locally*
*It wouldn't reproduce because the
--add-opens=java.base/java.lang=ALL-UNNAMED
option seems to break the JVM on my laptopI think that is unrelated to the CI failure though.
The text was updated successfully, but these errors were encountered: