From 82e1e44c9d0a76e5f33d4a8339f8a289e624837f Mon Sep 17 00:00:00 2001
From: Nikolai Kosjar <nikolai.kosjar@qt.io>
Date: Tue, 4 Jul 2017 11:17:28 +0200
Subject: [PATCH] Clang: Tests: Fix setFuture/connect order for QFutureWatacher

Change-Id: Iab177c17049451cb41ec8df16f9d47006b873e6a
Reviewed-by: Marco Bubke <marco.bubke@qt.io>
---
 tests/unit/unittest/chunksreportedmonitor.cpp | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/tests/unit/unittest/chunksreportedmonitor.cpp b/tests/unit/unittest/chunksreportedmonitor.cpp
index 479088c6efb..542a5936866 100644
--- a/tests/unit/unittest/chunksreportedmonitor.cpp
+++ b/tests/unit/unittest/chunksreportedmonitor.cpp
@@ -34,9 +34,9 @@ namespace ClangBackEnd {
 ChunksReportedMonitor::ChunksReportedMonitor(const QFuture<TextEditor::HighlightingResult> &future)
     : m_future(future)
 {
-    m_futureWatcher.setFuture(future);
     connect(&m_futureWatcher, &QFutureWatcher<TextEditor::HighlightingResult>::resultsReadyAt,
             this, &ChunksReportedMonitor::onResultsReadyAt);
+    m_futureWatcher.setFuture(future);
 }
 
 bool ChunksReportedMonitor::waitUntilFinished(int timeoutInMs)