Increase Flaky Timeout in testIlmHistoryIndexCanRollover (#62353) (#62402)

This busy assert easily takes about 5s on a very fast work station
so the default of 10s is not sufficient here at all.
This commit is contained in:
Armin Braun 2020-09-15 19:50:45 +02:00 committed by GitHub
parent 771a8893a6
commit 9ac4ee9c44
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 2 additions and 1 deletions

View File

@ -29,6 +29,7 @@ import org.elasticsearch.xpack.ilm.history.ILMHistoryStore;
import java.util.Arrays; import java.util.Arrays;
import java.util.Collection; import java.util.Collection;
import java.util.Collections; import java.util.Collections;
import java.util.concurrent.TimeUnit;
import static org.elasticsearch.cluster.metadata.IndexMetadata.SETTING_NUMBER_OF_REPLICAS; import static org.elasticsearch.cluster.metadata.IndexMetadata.SETTING_NUMBER_OF_REPLICAS;
import static org.elasticsearch.cluster.metadata.IndexMetadata.SETTING_NUMBER_OF_SHARDS; import static org.elasticsearch.cluster.metadata.IndexMetadata.SETTING_NUMBER_OF_SHARDS;
@ -115,7 +116,7 @@ public class ILMHistoryTests extends ESIntegTestCase {
//instead of failing the whole test change it to assertion error and wait some more time //instead of failing the whole test change it to assertion error and wait some more time
fail(e.getMessage()); fail(e.getMessage());
} }
}); }, 1L, TimeUnit.MINUTES);
//make sure ILM is stopped so no new items will be queued in ILM history //make sure ILM is stopped so no new items will be queued in ILM history
assertTrue(client().execute(StopILMAction.INSTANCE, new StopILMRequest()).actionGet().isAcknowledged()); assertTrue(client().execute(StopILMAction.INSTANCE, new StopILMRequest()).actionGet().isAcknowledged());