Extend timeout in RepositoryAnalysisFailureIT (#105287)

DaveCTurner · web-flow · commit cda94ac3ca99 · 2024-02-08T09:49:06.000-05:00
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
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
@@ -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) {

Original file line number	Diff line number	Diff line change
`@@ -423,7 +423,7 @@ public boolean acceptsEmptyRegister() {`
`423`	`423`	`}`
`424`	`424`
`425`	`425`	`private void analyseRepository(RepositoryAnalyzeAction.Request request) {`
`426`		`- client().execute(RepositoryAnalyzeAction.INSTANCE, request).actionGet(30L, TimeUnit.SECONDS);`
	`426`	`+ client().execute(RepositoryAnalyzeAction.INSTANCE, request).actionGet(5L, TimeUnit.MINUTES);`
`427`	`427`	`}`
`428`	`428`
`429`	`429`	`private static void assertPurpose(OperationPurpose purpose) {`