Details
-
Bug
-
Resolution: Done
-
P2: Important
-
None
-
5.14.0
-
None
Description
After migrating QFtp test to docker server, it becomes easier to hit "QTestEventLoop::instance().timeout()" during the test. The test seems to be inherently flaky and sensitive to timing.
To debug this issue, I turned on the debug flag (DUMP_SIGNALS) and extended the time of QTestEventLoop::enterLoop to 2 minutes. As shown in the log, the test kept waiting for the "commandFinished" response to QFtp::ConnectToHost command.
https://testresults.qt.io/coin/integration/qt/qtbase/tasks/web_rescheduled_qt_qtbase_1556804652830
https://codereview.qt-project.org/#/c/258132/15
agent:2019/05/02 15:02:25 build.go:197: QDEBUG : tst_QFtp::get(WithSocks5ProxyAndSession:nonExist01_1) [ 0.742 D] default tst_QFtp::commandStarted - 231:commandStarted( 231 ) agent:2019/05/02 15:02:25 build.go:197: QDEBUG : tst_QFtp::get(WithSocks5ProxyAndSession:nonExist01_1) [ 0.742 D] default tst_QFtp::stateChanged - 231: stateChanged( 1 ) agent:2019/05/02 15:02:25 build.go:197: QDEBUG : tst_QFtp::get(WithSocks5ProxyAndSession:nonExist01_1) [ 0.747 D] default tst_QFtp::stateChanged - 231: stateChanged( 3 ) agent:2019/05/02 15:04:26 build.go:197: FAIL! : tst_QFtp::get(WithSocks5ProxyAndSession:nonExist01_1) Network operation timed out on vsftpd.test-net.qt.local:21 agent:2019/05/02 15:04:26 build.go:197: Loc: [tst_qftp.cpp(691)]
Attachments
Issue Links
- relates to
-
QTBUG-76367 flaky tests in tst_qftp
- Closed