From 6766290699acd0d73c81cf690012d52729e518b9 Mon Sep 17 00:00:00 2001
From: Allan Sandfeld Jensen <allan.jensen@qt.io>
Date: Thu, 24 Nov 2016 10:58:43 +0100
Subject: Increase timeout in loadSignalsOrder tests

Use a standard QTRY_VERIFY. Apparently launching the web-process might
sometimes take more than 500ms on the CI under load.

Task-number: QTBUG-57119
Change-Id: Icb7706b5aed3cf72f026af6d1d2f9430c4942a2a
Reviewed-by: Peter Varga <pvarga@inf.u-szeged.hu>
Reviewed-by: Joerg Bornemann <joerg.bornemann@qt.io>
---
 tests/auto/widgets/qwebenginepage/tst_qwebenginepage.cpp | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

(limited to 'tests/auto/widgets/qwebenginepage/tst_qwebenginepage.cpp')

diff --git a/tests/auto/widgets/qwebenginepage/tst_qwebenginepage.cpp b/tests/auto/widgets/qwebenginepage/tst_qwebenginepage.cpp
index 518713b51..1629ec617 100644
--- a/tests/auto/widgets/qwebenginepage/tst_qwebenginepage.cpp
+++ b/tests/auto/widgets/qwebenginepage/tst_qwebenginepage.cpp
@@ -3410,7 +3410,7 @@ void tst_QWebEnginePage::loadSignalsOrder()
     SpyForLoadSignalsOrder loadSpy(&page);
     waitForSignal(&loadSpy, SIGNAL(started()), 500);
     page.load(url);
-    QTRY_VERIFY_WITH_TIMEOUT(loadSpy.isFinished(), 500);
+    QTRY_VERIFY(loadSpy.isFinished());
 }
 
 void tst_QWebEnginePage::undoActionHaveCustomText()
-- 
cgit v1.2.3