The mechanism employed where a CI test configuration would add
'NON_QTBASE_CMAKE_ARGS=-DFFMPEG_DIR={{.Env.FFMPEG_DIR}}' to its
environment variables to trigger QT_MEDIA_BACKEND=ffmpeg, was
needlessly indirect and based on conditions that didn't make
sense.
The logic now lives in the qtmultimedia repository.
Change-Id: I46b8fc1df45676b060157bfd670e9971980f0369
Reviewed-by: Lars Knoll <lars@knoll.priv.no>
This reverts commit d522c16201.
Reason for revert: This currently breaks CI, as declarative
and qtbase are in fact not warning free.
Change-Id: I52ecd7e845ea5ed3b47a6e7dd6426c6ac57b1095
Reviewed-by: Volker Hilsheimer <volker.hilsheimer@qt.io>
Many times there were warnings of comparison of signs which can go
unnoticed for various Android ABIs, so make warnings as errors
to make sure to catch such issues on the fly.
Change-Id: Idbc65bb3533188705ff7f7b9aaaf9de093817e4b
Reviewed-by: Volker Hilsheimer <volker.hilsheimer@qt.io>
macOS Catalina (10.15) has reached its end-of-life, and is no longer
supported with bug fixes or security updates by Apple.
Change-Id: Id8c222ee28f48b551c3522bfd353cf71be74d62e
Reviewed-by: Liang Qi <liang.qi@qt.io>
Reviewed-by: Heikki Halmet <heikki.halmet@qt.io>
We now have CMake 3.24 in CI, so we can re-enable the iOS tests.
Fixes: QTQAINFRA-5224
Change-Id: I742a9182299fb8ac6c52187a06a223a837d3968e
Reviewed-by: Toni Saario <toni.saario@qt.io>
Needed to fix iOS Xcode generator builds when using Xcode 14.
Otherwise compiler identification fails due to a code-signing error.
We hit it in our iOS MinimalStaticTests configuration.
error: Cannot code sign because the target does not have an
Info.plist file and one is not being generated
automatically.
(in target 'CompilerIdCXX' from project
'CompilerIdCXX')
See https://gitlab.kitware.com/cmake/cmake/-/issues/23719
Amends eee152ca70
Fixes: QTQAINFRA-5044
Change-Id: Idabd78e6e28816a8fc4dd7e627de82f2c622c54e
Reviewed-by: Alexey Edelev <alexey.edelev@qt.io>
non-threaded Wasm build will be built only in windows.
threaded wasm build will be done in macOS.
thread-asyncify wasm build will be done in linux.
Change-Id: Ibea96aca1ec4ce15c632ba2f4223d898f6ebffaa
Reviewed-by: Heikki Halmet <heikki.halmet@qt.io>
Add QT_ADDITIONAL_HOST_PACKAGES_PREFIX_PATH for Android and WASM
platforms to allow CMake find the host qtprotobufgen. The prefix points
to a host Protobuf package which qtprotobufgen depends on.
Change-Id: I2250614dceafb4b93a8a13ddb549f4ecc459436b
Reviewed-by: Mårten Nordheim <marten.nordheim@qt.io>
Windows 11 21H2 will be replaced by 22H2 version
Task-number: QTQAINFRA-5203
Pick-to: 6.4
Change-Id: Iad18055cf84d9c1ff38984611c820b1c23d663a2
Reviewed-by: Qt CI Bot <qt_ci_bot@qt-project.org>
Reviewed-by: Matti Paaso <matti.paaso@qt.io>
Add the minimal test preset for Multi-ABI Qt for Android.
Change-Id: Ic534daa5cea823b08b718f43ece637f9f9b375d9
Reviewed-by: Assam Boudjelthia <assam.boudjelthia@qt.io>
QtBase and QtWebview have still autotests failures with Android 12.
While waiting fixes let's prevent regression in other submodules
by adding those as blocking (significant).
Task-number: QTQAINFRA-4733
Change-Id: I6640e65b7efa5698557f97f1e195d50d58a41680
Reviewed-by: Jani Heikkinen <jani.heikkinen@qt.io>
Add FEATURE_thread=ON variant, with packaging enabled.
We now build the following configurations:
"webassembly" (all desktop hosts)
"webassembly-thread" (all desktop hosts)
"webassembly-thread-asyncify" (linux, for auto tests)
Change-Id: Iac212b350ed4a5551c00df4ac1cd579a1ccd05f2
Reviewed-by: David Skoland <david.skoland@qt.io>
Wasm will be built only in linux and those same binaries will be used also
in macOS and Windows.
Change-Id: If94098df624ab718491b9407c456d75ce7c7b117
Reviewed-by: Alexandru Croitor <alexandru.croitor@qt.io>
Other modules don't include needed flags
Change-Id: Id4525fa9887afff2ee6baed64f217167f545a2f5
Reviewed-by: Tommi Mänttäri <tommi.manttari@qt.io>
Reviewed-by: Toni Saario <toni.saario@qt.io>
Otherwise it doesn't find it and the build is configured without it.
Change-Id: Ib6b151c1177b4bde0de268f0a948a9a31f3a7225
Reviewed-by: Alexey Edelev <alexey.edelev@qt.io>
Reviewed-by: Ievgenii Meshcheriakov <ievgenii.meshcheriakov@qt.io>
Target blocks qtbase after eee152ca70
integrated. While 7390b668cd9ed7035f0b70d80476c11a480a1f15
is blocked by other issues, make target' tests insignificant to unblock
qtbase.
Change-Id: I84829e3588dc3d7ff593c27ba83abea5a667366d
Reviewed-by: Volker Hilsheimer <volker.hilsheimer@qt.io>
Reviewed-by: Tor Arne Vestbø <tor.arne.vestbo@qt.io>
Use templates which have Accessibility enabled for Squish.
Pick-to: 6.4
Task-number: QTQAINFRA-3559
Change-Id: If3c1a68a475149efdeb3bfd19efd6edaea411167
Reviewed-by: Johanna Äijälä <johanna.aijala@qt.io>
Reviewed-by: Ville-Pekka Karhu <ville-pekka.karhu@qt.io>
The configuration is not used to test qtbase, so dependency updates
might fail if changes already in qtbase do not pass when then updating
dependencies of qtdeclarative.
This happens right now in
https://testresults.qt.io/coin/integration/qt/qtdeclarative/tasks/1677711115
If we want to enable this configuration anywhere we need to add it to
qtbase, or ideally the default list of platforms in cmake_platforms.yaml.
Pick-to: 6.4
Change-Id: I3f5614d34def41caf1747a5f8094bac3aa2d9e2b
Reviewed-by: Fabian Kosmale <fabian.kosmale@qt.io>
Reviewed-by: Tor Arne Vestbø <tor.arne.vestbo@qt.io>
Use templates which have Accessibility enabled for
Squish.
Task-number: QTQAINFRA-3559
Pick-to: 6.4
Change-Id: I9538ea48791ea81738a41b1e101552cfc3bd454b
Reviewed-by: Ville-Pekka Karhu <ville-pekka.karhu@qt.io>
This broke after 8899244b8c which
unified the Android targets into one config file.
Pick-to: 6.4
Change-Id: I9b24973ddf716f97e72d152387365c35405e0502
Reviewed-by: Toni Saario <toni.saario@qt.io>
qdoc_qtattributionsscanner was also removed.
When we have TestDocs in the future, we need to rebuild
qdoc_qtattributionsscanner for Ubuntu 22.04.
Task-number: QTBUG-106948
Change-Id: I56bfda453cfddae97fa03b2a5eca91548152afe5
Reviewed-by: Topi Reiniö <topi.reinio@qt.io>
This reverts commit 7dcf1c8a4b.
tst_QNetworkReply::contentEncodingBigPayload() got fixed by new round
of qt5 submodule update on openSUSE 15.
Change-Id: I76de6742d0782dc1cef387c7f7ec2a7757fb5489
Reviewed-by: Liang Qi <liang.qi@qt.io>
- android armv7 is build only in windows
- android arm64 is build only in mac
- android x86 and android x86_64 are build only in linux
Task-number: QTBUG-101357
Pick-to: 6.4
Change-Id: Ibfbd2e3c6d5d3a7a52dde3b35ca6c23eddf4b2f1
Reviewed-by: Heikki Halmet <heikki.halmet@qt.io>
We need to verify latest Android NDK version in all
Qt6 branches and we need to retain the NDK version we
had when the specific branch was released at the first time.
Verification of the latest NDK will be done during integrations
in 'dev' branch and with older brances it will be done using
nightly build targets
Task-number: QTQAINFRA-4990
Change-Id: I2a96e419d403820f55f4244230c28ad09dc9095b
Reviewed-by: Qt CI Bot <qt_ci_bot@qt-project.org>
Reviewed-by: Assam Boudjelthia <assam.boudjelthia@qt.io>
New provisioned openSUSE will start failing to
tst_QNetworkReply::contentEncodingBigPayload. This should be fixed in
QTBUG-106016 but requires Qt5 submodule update which is blocked currently.
Meanwhile let's use Insignificant flag for openSUSE autotests to get
provisioning changes in.
Change-Id: Ib9a8b61f35f6e105440308af44c2d96605ea3b27
Reviewed-by: Jani Heikkinen <jani.heikkinen@qt.io>
The way of running bic tests has changed. Now tests need to be run on
qt5 level where all modules are present and intermodule includes can
be handled.
Task-number: QTBUG-100698
Change-Id: Ic68c019988718485201602f279530c501f6e6ba3
Reviewed-by: Qt CI Bot <qt_ci_bot@qt-project.org>
Reviewed-by: Simo Fält <simo.falt@qt.io>
We don't need the license check when verifying macOS 13 compatibility.
Change-Id: Ib39e187ae339c0754719773f8317ead17328f201
Reviewed-by: Toni Saario <toni.saario@qt.io>
SLES 15 SP3 will be replaced by SLES 15 SP4
Task-number: QTQAINFRA-5068
Change-Id: I60f0ec02d71d1db162f1238df7ad853ff0df2d6e
Reviewed-by: Tony Sarajärvi <tony.sarajarvi@qt.io>
