From 93b52c925d8f82d3d5dcba9d6056a27f5af88415 Mon Sep 17 00:00:00 2001 From: Simon Willnauer Date: Fri, 28 Nov 2014 12:27:55 +0100 Subject: [PATCH] [TEST] With pipelining disabled requests can come back in any order Closes #8697 --- .../http/netty/NettyPipeliningDisabledIntegrationTest.java | 5 ++--- 1 file changed, 2 insertions(+), 3 deletions(-) diff --git a/src/test/java/org/elasticsearch/http/netty/NettyPipeliningDisabledIntegrationTest.java b/src/test/java/org/elasticsearch/http/netty/NettyPipeliningDisabledIntegrationTest.java index 7372b47d57b..349631588bd 100644 --- a/src/test/java/org/elasticsearch/http/netty/NettyPipeliningDisabledIntegrationTest.java +++ b/src/test/java/org/elasticsearch/http/netty/NettyPipeliningDisabledIntegrationTest.java @@ -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 */ private void assertResponsesOutOfOrder(List opaqueIds) { - String message = String.format(Locale.ROOT, "Expected returned http message ids to be out of order: %s", opaqueIds); - assertThat(opaqueIds, hasItems("0", "1", "2", "3", "4", "5", "6")); - assertThat(message, opaqueIds, not(contains("0", "1", "2", "3", "4", "5", "6"))); + String message = String.format(Locale.ROOT, "Expected returned http message ids to be in any order of: %s", opaqueIds); + assertThat(message, opaqueIds, containsInAnyOrder("0", "1", "2", "3", "4", "5", "6")); } }