[TEST] With pipelining disabled requests can come back in any order
Closes #8697
This commit is contained in:
parent
5c6c7f23ba
commit
93b52c925d
|
@ -71,8 +71,7 @@ public class NettyPipeliningDisabledIntegrationTest extends ElasticsearchIntegra
|
||||||
* checks if all responses are there, but also tests that they are out of order because pipelining is disabled
|
* checks if all responses are there, but also tests that they are out of order because pipelining is disabled
|
||||||
*/
|
*/
|
||||||
private void assertResponsesOutOfOrder(List<String> opaqueIds) {
|
private void assertResponsesOutOfOrder(List<String> opaqueIds) {
|
||||||
String message = String.format(Locale.ROOT, "Expected returned http message ids to be out of order: %s", opaqueIds);
|
String message = String.format(Locale.ROOT, "Expected returned http message ids to be in any order of: %s", opaqueIds);
|
||||||
assertThat(opaqueIds, hasItems("0", "1", "2", "3", "4", "5", "6"));
|
assertThat(message, opaqueIds, containsInAnyOrder("0", "1", "2", "3", "4", "5", "6"));
|
||||||
assertThat(message, opaqueIds, not(contains("0", "1", "2", "3", "4", "5", "6")));
|
|
||||||
}
|
}
|
||||||
}
|
}
|
||||||
|
|
Loading…
Reference in New Issue