From f15147b87bf06f478e6fc2f56d6c345dcf3d2efa Mon Sep 17 00:00:00 2001 From: Adrien Grand Date: Wed, 19 Jul 2017 17:29:49 +0200 Subject: [PATCH] Remove assumption about how the timeout feature is implemented. Original commit: elastic/x-pack-elasticsearch@7a4fa000c1694d81a5d46e745736592f80d65016 --- .../org/elasticsearch/xpack/graph/test/GraphTests.java | 7 +------ 1 file changed, 1 insertion(+), 6 deletions(-) diff --git a/plugin/src/test/java/org/elasticsearch/xpack/graph/test/GraphTests.java b/plugin/src/test/java/org/elasticsearch/xpack/graph/test/GraphTests.java index 07c8d7f7e49..b903a7bc518 100644 --- a/plugin/src/test/java/org/elasticsearch/xpack/graph/test/GraphTests.java +++ b/plugin/src/test/java/org/elasticsearch/xpack/graph/test/GraphTests.java @@ -236,12 +236,7 @@ public class GraphTests extends XPackSingleNodeTestCase { // Most of the test runs we reach dave in the allotted time before we hit our // intended delay but sometimes this doesn't happen so I commented this line out. - // checkVertexDepth(response, 1, "dave"); - - // This is the point where we should certainly have run out of time due - // to the test query plugin with a deliberate pause - assertNull("Should have timed out trying to crawl out to kurt", response.getVertex(Vertex.createId("people","kurt"))); - + // checkVertexDepth(response, 1, "dave"); } public void testNonDiversifiedCrawl() {