- 
    
Bug
 - 
    Resolution: Done
 - 
    
P3: Somewhat important
 - 
    5.0.0
 - 
    None
 - 
    Windows 7 32-bit, MSVC 2010
 
- 
        89245069921c5de7e748c289647c2af16c71c499 , 274c25852179d032efb5afe6a4a268c7fafc9e8c
 
Since approx. 2nd June, autotests on Windows which use QProcess to test some Qt tool have a greatly increased rate of hanging.
The affected tests include at least:
- tst_moc - http://testresults.qt-project.org/ci/QtBase_master_Integration/build_03009/win32-msvc2010_developer-build_qtnamespace_Windows_7/log.txt.gz
 - tst_qmake - http://testresults.qt-project.org/ci/QtBase_master_Integration/build_02997/win32-msvc2010_Windows_7/log.txt.gz
 - tst_uic - http://testresults.qt-project.org/ci/QtBase_master_Integration/build_03012/win32-msvc2010_Windows_7/log.txt.gz
 
It could be a coincidence, or it could be some recent change in qtbase destabilizing QProcess on Windows.
- relates to
 - 
                    
QTBUG-26024 QProcess on Windows warns "QTimer can only be used with threads started with QThread" if no application object
-         
 - Closed
 
 -         
 
| For Gerrit Dashboard: QTBUG-26023 | ||||||
|---|---|---|---|---|---|---|
| # | Subject | Branch | Project | Status | CR | V | 
| 27919,1 | Replace QTEST_APPLESS_MAIN with QTEST_MAIN in tests using QProcess | master | qt/qtbase | Status: MERGED | +2 | 0 |