P1: Critical tst_QProcess::processEventsInAReadyReadSlot(no waitForReadyRead) has failed also earlier, but very rarely, but within the last week it has failed 80 times in the CI on Ubuntu 16.04, RHEL 7.2 and RHEL 6.6 (in 5.9.2 and 5.10.0).
********* Start testing of tst_QProcess ********* Config: Using QtTest library 5.10.0, Qt 5.10.0 (x86_64-little_endian-lp64 shared (dynamic) release build; by GCC 5.3.1 20160406 (Red Hat 5.3.1-6)) PASS : tst_QProcess::initTestCase() FAIL! : tst_QProcess::processEventsInAReadyReadSlot(no waitForReadyRead) 'process.waitForFinished()' returned FALSE. () Loc: [../tst_qprocess.cpp(2487)] PASS : tst_QProcess::processEventsInAReadyReadSlot(waitForReadyRead) PASS : tst_QProcess::cleanupTestCase() Totals: 3 passed, 1 failed, 0 skipped, 0 blacklisted, 30045ms ********* Finished testing of tst_QProcess *********
Links to test logs:
- relates to
-
QTBUG-24451 windows - QAbstractSocket::waitForXXX functions are unreliable
-
- Open
-
| For Gerrit Dashboard: QTBUG-62584 | ||||||
|---|---|---|---|---|---|---|
| # | Subject | Branch | Project | Status | CR | V |
| 202801,4 | QProcess/Unix: fix possible race condition inside waitForXXX() loops | 5.9 | qt/qtbase | Status: MERGED | +2 | 0 |
| 202982,9 | Avoid more deadlocks if QProcess state changes in a slot | 5.9 | qt/qtbase | Status: ABANDONED | -1 | 0 |
| 203594,1 | Avoid more deadlocks if QProcess state changes in a slot | dev | qt/qtbase | Status: ABANDONED | 0 | 0 |