Fix unit tests: Set timeout long enough

Unit tests wait for BlueZ to come back after at most 20 seconds.
On Andreas' machine, BlueZ scans for about 25 seconds, causing
tests to fail. This patch increses the timeout to 26.5 seconds.

Change-Id: I4cabc6a20231cb7d148660b2d951ba77b32c0a2f
Reviewed-by: Alex Blasche <alexander.blasche@qt.io>
This commit is contained in:
Andreas Buhr 2021-03-09 12:24:21 +01:00
parent f1c04f8c93
commit 091da38e7b
2 changed files with 2 additions and 2 deletions

View File

@ -120,7 +120,7 @@ void tst_QLowEnergyCharacteristic::initTestCase()
<< remoteDevice.address() << remoteDevice.deviceUuid();
controller->connectToDevice();
QTRY_IMPL(controller->state() != QLowEnergyController::ConnectingState,
20000);
26500);
if (controller->state() != QLowEnergyController::ConnectedState) {
// any error and we skip
delete controller;

View File

@ -110,7 +110,7 @@ void tst_QLowEnergyDescriptor::initTestCase()
qDebug() << "Connecting to" << remoteDeviceInfo.address();
controller->connectToDevice();
QTRY_IMPL(controller->state() != QLowEnergyController::ConnectingState,
20000)
26500)
if (controller->state() != QLowEnergyController::ConnectedState) {
// any error and we skip
delete controller;