0b4446e16f
If a test returns 0 but writes an XML logfile that contains FAIL or a corrupted XML file, then qt-testrunner considers it a CRASH and exits with 3. Previously any test execution returning 0 (success) was considered a PASS. Changing this behavior with this patch finds a lot of test crashes on Android (QTBUG-100470), because the tests are run indirectly on the emulator and the test wrapper process could not detect the crash, thus returning 0 to qt-testrunner. But the corrupt XML file is caught now. Likewise, if a test returns != 0 but the XML logfile contains only PASS, qt-testrunner considers it a FAIL. This used to be the case but now tests are added. Finally changed logging for such cases from INFO to WARNING. Task-number: QTBUG-100470 Change-Id: I404c9d2211c7de027bf776d1914519d37f513ca1 Reviewed-by: Assam Boudjelthia <assam.boudjelthia@qt.io> |
||
---|---|---|
.. | ||
accessibilityinspector | ||
aglfn | ||
android | ||
cmake | ||
edid | ||
glgen | ||
gradientgen | ||
includemocs | ||
integrity | ||
lexgen | ||
locale_database | ||
plugintest | ||
qfloat16-tables | ||
testrunner | ||
unicode | ||
wasm | ||
x86simdgen | ||
xkbdatagen |