Timur Pocheptsov c668fd940d Fix 'out of process' autotests ... We are, arguably, not testing QProcess and its ability to start or finish, we test QUdpSocket. If, for some reason (as we discovered on some specific machines recently) the process does not start or does not produce any output (canReadLine), we QSKIP instead of failing. Also, all those QCOMPARE will bypass the part there we stop processes - so must be RAII-protected. Fixes: QTBUG-82717 Change-Id: Idfb0d4a483d753f336b3827875eeaf51c79270e2 Reviewed-by: Volker Hilsheimer <volker.hilsheimer@qt.io>		2020-03-11 18:23:24 +00:00
..
access	tst_qnetworkreply: Print proxy warning to stderr instead of stdout	2020-02-05 15:01:10 +00:00
bearer	Add cmdline feature to qmake	2019-02-18 07:12:14 +00:00
kernel	tst_QNetworkInterface: don't force an IPv4 link-local address	2019-12-07 10:20:27 -08:00
selftest	Skip instead of fail tests when test server is not available	2020-01-14 00:15:16 +01:00
socket	Fix 'out of process' autotests	2020-03-11 18:23:24 +00:00
ssl	Flatten version-specific blacklisting on macOS to all macOS versions	2020-01-22 17:58:31 +01:00
network.pro	Skip instead of fail tests when test server is not available	2020-01-14 00:15:16 +01:00