Details
-
Bug
-
Resolution: Fixed
-
P1: Critical
-
dev
-
None
-
-
7bc6a1c86 (dev), 2f0726c8c (6.7), bba26d722 (dev), 5260dcc61 (6.7), a9f16c0ab (dev), feff219aa (dev), 471098918 (dev), 4244b4194 (dev), 772fd609c (dev), 715e9f618 (6.7), 21ff70afb (6.7), a4be920e1 (6.7), 34d856be2 (6.7), 002d6cb2a (tqtc/lts-6.5)
-
2023wk48FOQtforAndroid, 2023wk50FOQtforAndroid, 2024wk02FOQtforAndroid, 2024wk04FOQtforAndroid, 2024wk06FOQtforAndroid, 2024wk08FOQtforAndroid, 2024wk10FOQtforAndroid, 2024wk12FOQtforAndroid, 2024wk14FOQtforAndroid
Description
When running Android NDK r26b in Coin - Android 14 tests have begun to fail consistently.
I have run r26b three times against Android-14, all have given the same fail, latest run:
https://coin.ci.qt.io/coin/integration/qt/qt5/tasks/web_qt_qt5_1701681683523
Test
qt/qtbase 24627d9bce444cee6bc593680c494d58ec241171
The following tests FAILED: 461 - tst_qrhiwidget (Failed) 462 - tst_qdom (Failed) 463 - tst_gestures (Failed) 464 - tst_languagechange (Failed) 465 - tst_qfocusevent (Failed) 466 - tst_qsharedpointer_and_qwidget (Failed) 467 - tst_qnetworkaccessmanager_and_qprogressdialog (Failed) 468 - tst_networkselftest (Failed) 469 - tst_qaccessibility (Failed) 470 - tst_qcomplextext (Failed) 471 - tst_qobjectrace (Failed) 472 - tst_toolsupport (Failed) 473 - tst_android_deployment_settings (Failed) 474 - tst_baseline_painting (Failed) 475 - tst_baseline_widgets (Failed) 476 - tst_baseline_stylesheet (Failed) 477 - tst_baseline_text (Failed) Errors while running CTest Process finished with error: exit status 8
I checked if this is an issue with current dev branch (with NDK r25b), two nightly runs have failed the same tests:
2023-12-04 01:04:09
https://testresults.qt.io/coin/integration/qt/qt5/tasks/nightly1704905214
2023-12-03 01:04:01
https://testresults.qt.io/coin/integration/qt/qt5/tasks/nightly1704888222
There were many Qtbase changes made recently to Android, Coin integration of that passed:
https://testresults.qt.io/coin/integration/qt/qtbase/tasks/1704829526
I think a key difference is what provisioning VM was used for the runs. Qtbase integration run used a provision VM that was created 2023-11-21. Nightlies/health checks build and use fresh provisions for their runs. Something is inconsistent with Android scripts / emulator in provisioning.
UPDATE (Jan 11 2024):
This issue seems to be back and now failing dev and 6.7 for tst_qrhiwidget. It might be related to https://developer.android.com/studio/releases/emulator#33-1-23 update that adds support for Vulkan 1.3. We had a patch for 6.6 and 6.5 https://codereview.qt-project.org/c/qt/qt5/+/527815 to use the emulator version that used to work, that seemed to help with tst_rhi test on 6.6 and 6.5 branches but not with tst_qrhiwidget on dev.
Also, locally using the old emulator seems to also fix the issue and without I get a crash (attached) but on CI we get different behavior where the emulator version doesn't seem to affect anything.
Attachments
Issue Links
- blocks
-
QTQAINFRA-5771 NDK update to NDK r26b
- Closed
- is blocked by
-
QTBUG-120164 qtquick3d fails - ERROR building: Timeout after 15m0s: No output received on CI
- Closed
- relates to
-
QTBUG-118717 Vulkan fails on android-14-RHEL-8.8-x86_64-on-linux emulator
- Closed
-
QTBUG-118840 [Crash] Vulkan examples crash on Android when unlocking the screen
- Closed