-
Notifications
You must be signed in to change notification settings - Fork 25.2k
[CI] S3BlobStoreRepositoryTests testMetrics failing #101608
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
Comments
Pinging @elastic/es-distributed (Team:Distributed) |
Relabel this to lwo-risk since it is an off-by-one error in metric number comparison which is not a critical path. |
I think this is likely a duplicate of #88841 |
In #101608 we saw one of these assertions fail, but it's impossible to know which one without some more details. This commit adds descriptions to the assertions in the loop.
With logging restriction (elastic#105020), the networkTrace flag needs to be set for AWS request debug logging. Relates: elastic#101608
In elastic#101608 we saw one of these assertions fail, but it's impossible to know which one without some more details. This commit adds descriptions to the assertions in the loop.
It still has not failed yet since May 28. |
We're awaiting more information about failures of this test, so we need to actually run it occasionally... Relates elastic#101608
We're awaiting more information about failures of this test, so we need to actually run it occasionally... Relates elastic#101608
I've been running this test over the past couple of days with stress-ng on and off randomly. over 20k+ runs and no failure. IMO, we can close it since it doesn't reproduce. |
I also couldn't reproduce it on repeated but it was failing very rarely in CI even before we muted it. I still think it's an issue tho. |
Pinging @elastic/es-distributed-coordination (Team:Distributed Coordination) |
If sending request fails locally without reaching the server, the retryable exception is logged differently. This PR enables the logging for this scenario. Relates: elastic#88841 Relates: elastic#101608
If sending request fails locally without reaching the server, the retryable exception is logged differently. This PR enables the logging for this scenario. Relates: elastic#88841 Relates: elastic#101608 (cherry picked from commit 5204902) # Conflicts: # modules/repository-s3/src/internalClusterTest/java/org/elasticsearch/repositories/s3/S3BlobStoreRepositoryTests.java
If sending request fails locally without reaching the server, the retryable exception is logged differently. This PR enables the logging for this scenario. Relates: #88841 Relates: #101608 (cherry picked from commit 5204902) # Conflicts: # modules/repository-s3/src/internalClusterTest/java/org/elasticsearch/repositories/s3/S3BlobStoreRepositoryTests.java
If sending request fails locally without reaching the server, the retryable exception is logged differently. This PR enables the logging for this scenario. Relates: elastic#88841 Relates: elastic#101608
If sending request fails locally without reaching the server, the retryable exception is logged differently. This PR enables the logging for this scenario. Relates: elastic#88841 Relates: elastic#101608
If sending request fails locally without reaching the server, the retryable exception is logged differently. This PR enables the logging for this scenario. Relates: elastic#88841 Relates: elastic#101608
Since last update (2 month ago), there has not been any actual CI failure. The only failure is unrelated and due to testing of upload checksum. |
No new failure. Keep waiting ... |
This hasn't failed in the last month, I think that means it's been 4 months since it failed. I'm inclined to close this? Failures in last month: https://es-delivery-stats.elastic.dev/app/r/s/uOoHS |
With the AWS SDK now upgraded to v2 in #126843 I believe this test failure is now either gone or, at the very least, changed beyond all recognition, so I'm closing it. |
Build scan:
https://gradle-enterprise.elastic.co/s/cmzydsjar4s3c/tests/:modules:repository-s3:internalClusterTest/org.elasticsearch.repositories.s3.S3BlobStoreRepositoryTests/testMetrics
Reproduction line:
Applicable branches:
main
Reproduces locally?:
No
Failure history:
https://gradle-enterprise.elastic.co/scans/tests?tests.container=org.elasticsearch.repositories.s3.S3BlobStoreRepositoryTests&tests.test=testMetrics
Failure excerpt:
The text was updated successfully, but these errors were encountered: