From 54d6e3ad7b96c044ea56c8c44ca7937cdd76e1f2 Mon Sep 17 00:00:00 2001
From: Christian Stenger <christian.stenger@qt.io>
Date: Wed, 9 May 2018 09:04:31 +0200
Subject: [PATCH] Valgrind: Fix unit test

Change-Id: I270aaf2fd2b74a6d1ec067555a9f65ecbab2ffad
Reviewed-by: hjk <hjk@qt.io>
---
 src/plugins/valgrind/valgrindmemcheckparsertest.cpp | 3 ++-
 1 file changed, 2 insertions(+), 1 deletion(-)

diff --git a/src/plugins/valgrind/valgrindmemcheckparsertest.cpp b/src/plugins/valgrind/valgrindmemcheckparsertest.cpp
index ad4f5a45d05..3350895753e 100644
--- a/src/plugins/valgrind/valgrindmemcheckparsertest.cpp
+++ b/src/plugins/valgrind/valgrindmemcheckparsertest.cpp
@@ -457,7 +457,8 @@ void ValgrindMemcheckParserTest::testParserStop()
 {
     ValgrindRunner runner;
     runner.setValgrindExecutable(fakeValgrindExecutable());
-    runner.setValgrindArguments({"-i", dataFile("memcheck-output-sample1.xml"), "--wait", "5" });
+    runner.setValgrindArguments({QString("--xml-socket=127.0.0.1:%1").arg(m_server->serverPort()),
+                                 "-i", dataFile("memcheck-output-sample1.xml"), "--wait", "5" });
     runner.setProcessChannelMode(QProcess::ForwardedChannels);
 
     runner.setDevice(ProjectExplorer::DeviceManager::instance()->defaultDevice(