-
Bug
-
Resolution: Unresolved
-
P2: Important
-
None
-
production
-
None
In this other Teams thread about tst_qquickpopup failing, we can see that the test has been crashing for multiple people 100% of the time locally, but the CI seems to pass it sometimes. For example look at https://testresults.qt.io/coin/integration/qt/qtdeclarative/tasks/1755553310 (check android-15-x86_64-on-linux target).
Looking at the log files (androidtestrunner-1755561648641.txt) it shows that the test crashes at the and doesn't finish running all the test cases. Then, there's another attempt to run only the test case that failed (fadedimmer at androidtestrunner-1755561720150.txt
) but the other test cases after that case don't seem to be run at all and the whole test is marked as passed after that. The android test runner correctly returns that the test failed in the first time, so I'm assuming this has to do with the test output processing and re-run logic?
- relates to
-
QTBUG-139211 tst_qquickpopup (Failed)
-
- Closed
-
- resulted in
-
QTBUG-139332 Theme variations of tests: Basic, Fusion, FluentWinUI3 etc
-
- Reported
-
-
QTBUG-139333 QtTest after a fatal error can report completion with no hint of omissions
-
- Open
-
-
QTQAINFRA-7351 qt-testrunner.py does not record the test executable properly on Android
-
- In Review
-
-
QTQAINFRA-7378 qt-testrunner.py should parse the messages for QFatal and treat test like a crash
-
- Open
-
-
QTQAINFRA-7379 coin_scraper.py should parse the messages for QFatal and mark the test as CRASH in the testresults database
-
- Open
-