-
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] GoogleCloudStorageBlobContainerRetriesTests.testWriteLargeBlob #52430
Labels
:Distributed Coordination/Snapshot/Restore
Anything directly related to the `_snapshot/*` APIs
>test-failure
Triaged test failures from CI
Comments
astefan
added
:Distributed Coordination/Snapshot/Restore
Anything directly related to the `_snapshot/*` APIs
>test-failure
Triaged test failures from CI
labels
Feb 17, 2020
Pinging @elastic/es-distributed (:Distributed/Snapshot/Restore) |
original-brownbear
added a commit
to original-brownbear/elasticsearch
that referenced
this issue
Feb 17, 2020
Same as elastic#51933 but for the custom handler just used in this test. Closes elastic#52430
original-brownbear
added a commit
that referenced
this issue
Feb 18, 2020
original-brownbear
added a commit
to original-brownbear/elasticsearch
that referenced
this issue
Feb 18, 2020
Same as elastic#51933 but for the custom handler just used in this test. Closes elastic#52430
original-brownbear
added a commit
to original-brownbear/elasticsearch
that referenced
this issue
Feb 18, 2020
Same as elastic#51933 but for the custom handler just used in this test. Closes elastic#52430
original-brownbear
added a commit
that referenced
this issue
Feb 18, 2020
original-brownbear
added a commit
that referenced
this issue
Feb 18, 2020
tlrx
added a commit
that referenced
this issue
Mar 5, 2020
Tests in GoogleCloudStorageBlobStoreRepositoryTests are known to be flaky on JDK 8 (#51446, #52430 ) and we suspect a JDK bug (https://bugs.openjdk.java.net/browse/JDK-8180754) that triggers some assertion on the server side logic that emulates the Google Cloud Storage service. Sadly we were not able to reproduce the failures, even when using the same OS (Debian 9, Ubuntu 16.04) and JDK (Oracle Corporation 1.8.0_241 [Java HotSpot(TM) 64-Bit Server VM 25.241-b07]) of almost all the test failures on CI. While we spent some time fixing code (#51933, #52431) to circumvent the JDK bug they are still flaky on JDK-8. This commit mute these tests for JDK-8 only. Close ##52906
tlrx
added a commit
that referenced
this issue
Mar 5, 2020
Tests in GoogleCloudStorageBlobStoreRepositoryTests are known to be flaky on JDK 8 (#51446, #52430 ) and we suspect a JDK bug (https://bugs.openjdk.java.net/browse/JDK-8180754) that triggers some assertion on the server side logic that emulates the Google Cloud Storage service. Sadly we were not able to reproduce the failures, even when using the same OS (Debian 9, Ubuntu 16.04) and JDK (Oracle Corporation 1.8.0_241 [Java HotSpot(TM) 64-Bit Server VM 25.241-b07]) of almost all the test failures on CI. While we spent some time fixing code (#51933, #52431) to circumvent the JDK bug they are still flaky on JDK-8. This commit mute these tests for JDK-8 only. Close ##52906
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
:Distributed Coordination/Snapshot/Restore
Anything directly related to the `_snapshot/*` APIs
>test-failure
Triaged test failures from CI
There are two similar failures for this test, but I am not 100% sure this is network related or a test failure, but opening this one for further investigation.
This one from today: https://gradle-enterprise.elastic.co/s/wpojzqhezgkhm/console-log#L4309
This one from Feb 9th: https://gradle-enterprise.elastic.co/s/tk2o44alzkal2/console-log#L4324
Both report a Socket closed exception:
But today's one has something more, from the GCP side:
The text was updated successfully, but these errors were encountered: