From cda94ac3ca9904fd1d6b19f4905c29f2a134bfe6 Mon Sep 17 00:00:00 2001 From: David Turner Date: Thu, 8 Feb 2024 14:49:06 +0000 Subject: [PATCH] Extend timeout in RepositoryAnalysisFailureIT (#105287) We see occasional test failures in CI due to the analysis not completing within this 30s timeout. It doesn't look like anything is actually wrong, the test machine is just busy and these tests can be quite IO-intensive. This commit gives them more time. Closes #99422 --- .../blobstore/testkit/RepositoryAnalysisFailureIT.java | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/x-pack/plugin/snapshot-repo-test-kit/src/internalClusterTest/java/org/elasticsearch/repositories/blobstore/testkit/RepositoryAnalysisFailureIT.java b/x-pack/plugin/snapshot-repo-test-kit/src/internalClusterTest/java/org/elasticsearch/repositories/blobstore/testkit/RepositoryAnalysisFailureIT.java index e79186d886925..025516f8529ae 100644 --- a/x-pack/plugin/snapshot-repo-test-kit/src/internalClusterTest/java/org/elasticsearch/repositories/blobstore/testkit/RepositoryAnalysisFailureIT.java +++ b/x-pack/plugin/snapshot-repo-test-kit/src/internalClusterTest/java/org/elasticsearch/repositories/blobstore/testkit/RepositoryAnalysisFailureIT.java @@ -423,7 +423,7 @@ public boolean acceptsEmptyRegister() { } private void analyseRepository(RepositoryAnalyzeAction.Request request) { - client().execute(RepositoryAnalyzeAction.INSTANCE, request).actionGet(30L, TimeUnit.SECONDS); + client().execute(RepositoryAnalyzeAction.INSTANCE, request).actionGet(5L, TimeUnit.MINUTES); } private static void assertPurpose(OperationPurpose purpose) {