Changed firewall configurations in CI network caused W10 VMs to prompt
to select public/private network profile setting for the changed
network.
Set the network profile with a script to prevent this prompt reappearing
in build/test VMs.
Pick-to: 6.11 6.8
Change-Id: I6c71fd31cd3982742254edf508a0ccfc3d2ceeb6
Reviewed-by: Toni Saario <toni.saario@qt.io>
(cherry picked from commit 862c3df5bf)
Reviewed-by: Qt Cherry-pick Bot <cherrypick_bot@qt-project.org>
Set them as InsignificantTests.
Task-number: QTQAINFRA-7579
Change-Id: I58df5bcd55e9b4e11a733c0a0576d6ec2f743ebe
Reviewed-by: Oliver Wolff <oliver.wolff@qt.io>
(cherry picked from commit b5af653382)
Reviewed-by: Qt Cherry-pick Bot <cherrypick_bot@qt-project.org>
This target builds Qt6 as arm64ec on a x86_64 host. The provisioning is
done through x86_64 so many of the 3rd party dependencies (e.g. ffmpeg)
are x86_64.
Task-number: QTQAINFRA-7579
Change-Id: I66b2a6b70667586cddf1df8b96c3e1149fac4567
Reviewed-by: Alexandru Croitor <alexandru.croitor@qt.io>
Reviewed-by: Oliver Wolff <oliver.wolff@qt.io>
(cherry picked from commit fc6d6d66cc)
Reviewed-by: Qt Cherry-pick Bot <cherrypick_bot@qt-project.org>
Tier-1 image changes in -73:
- MSVC 14.44.35211.0
- Windows SDK 10.0.26100.7705
- installed .NET SDK
- Visual Studio now has 'ci_msvs' user added with a license to use
debugger tools.
[CI Platforms]
Pick-to: 6.11 6.8
Task-number: QTQAINFRA-7726
Task-number: QTQAINFRA-5417
Change-Id: I67d5605c544228daa6bac502ac487d1d5060fd81
Reviewed-by: Simo Fält <simo.falt@qt.io>
(cherry picked from commit 99c69904b8)
Reviewed-by: Qt Cherry-pick Bot <cherrypick_bot@qt-project.org>
Syft is a tool that scans package manager manifest or lock files and
generates an SBOM (Software Bill of Materials) file based on the
found packages. It can generated both CycloneDX and SPDX SBOM formats.
The tool will be used by the Qt for Python project to generate SBOMs
based on the python packages used during the build.
The tool is provisioned on all the platforms that have the
GenerateSBOM feature.
Pick-to: 6.11 6.8
Task-number: PYSIDE-3366
Change-Id: I1369f7b1b041b1fc0d8a56a20446df322d26d33a
Reviewed-by: Joerg Bornemann <joerg.bornemann@qt.io>
(cherry picked from commit 341fe4e602)
Reviewed-by: Qt Cherry-pick Bot <cherrypick_bot@qt-project.org>
Except 'opensuse-15.6-host-asan' -target which will be handled in:
- "Port the ASAN config from OpenSUSE 15 to 16" (QTQAINFRA-7660)
[CI Platforms]
Pick-to: 6.11
Task-number: QTQAINFRA-7455
Task-number: QTQAINFRA-7452
Change-Id: Ibd224779c77fa2af9460c240181cbe341ae454a9
Reviewed-by: Simo Fält <simo.falt@qt.io>
(cherry picked from commit 3f495a95ee)
The TIFF and WEBP image format plugins opportunistically link the system
libtiff/libwebp whenever find_package() succeeds. When the Linux release
packaging host moved from RHEL 8.10 to RHEL 9.6, libtiff-devel became
present (pulled in transitively via gtk3-devel), so the shipped libqtiff
plugin gained a hard dependency on libtiff.so.5, breaking on hosts that
ship a different libtiff soname (e.g. libtiff.so.6).
Pin tiff and webp to the bundled copies in the Linux desktop packaging
configurations (rhel-9.6 and ubuntu-24.04-arm64) so the released
binaries stay self-contained regardless of what is installed on the
build host.
Fixes: QTBUG-147470
Pick-to: 6.11
Change-Id: If406fd6b9338af51176b50c3af5bb3193fd226fd
Reviewed-by: Volker Hilsheimer <volker.hilsheimer@qt.io>
Reviewed-by: Kai Köhne <kai.koehne@qt.io>
(cherry picked from commit 2882b5615b)
Reviewed-by: Qt Cherry-pick Bot <cherrypick_bot@qt-project.org>
qtbase for now, as some of the submodules fail to build
examples in this mode.
Task-number: QTBUG-90820
Task-number: QTBUG-96232
Change-Id: Icb2254bafcbeee7e4bba7500b2a8395f386244ef
Reviewed-by: Alexandru Croitor <alexandru.croitor@qt.io>
(cherry picked from commit 5d41389310)
Reviewed-by: Qt Cherry-pick Bot <cherrypick_bot@qt-project.org>
$VCPKG_ROOT/packages/ fills up later in install-vcpkg-ports.sh, clean up
at the end of that script.
This amends 75cdce7b2c
Pick-to: 6.11 6.8
Change-Id: I87cf73c5b46733141d017efa6d4a2e9e6c482424
Reviewed-by: Joerg Bornemann <joerg.bornemann@qt.io>
(cherry picked from commit 5e9c31fe74)
Reviewed-by: Qt Cherry-pick Bot <cherrypick_bot@qt-project.org>
This prevents sneaky NDK overwrites if there is no versioning in the
.zip root directory.
Pick-to: 6.11 6.8
Task-number: QTQAINFRA-7069
Change-Id: Ib0bd30c27da316735001bc5027d1dac1f8ead703
Reviewed-by: Assam Boudjelthia <assam.boudjelthia@qt.io>
(cherry picked from commit 7c5594ea08)
Reviewed-by: Qt Cherry-pick Bot <cherrypick_bot@qt-project.org>
In preparation of consolidating the OHOS target-architecture variables
onto OHOS_ARCH and droppeding OHOS_ABI, we're updating the HarmonyOS
target platform configs to pass -DOHOS_ARCH=arm64-v8a.
This doesn't change behavior, because OHOS_ABI defaults to arm64-v8a.
Task-number: QTBUG-147291
Change-Id: I1d0d2071d0512f976eaa031d7c976aa97c3bc9cb
Reviewed-by: Simo Fält <simo.falt@qt.io>
(cherry picked from commit 3275891741)
The app no longer ships with any platforms (SDKs) built in
except for the macOS platform.
Change-Id: I83200553f52b9edf80212a12bb9abd6a26f27407
Reviewed-by: Volker Hilsheimer <volker.hilsheimer@qt.io>
(cherry picked from commit 50086ff8f3)
Reviewed-by: Qt Cherry-pick Bot <cherrypick_bot@qt-project.org>
The FFmpeg components 'avdevice' and 'avfilter' are not used in Qt.
By not building them, we save some time during provisioning in CI.
Pick-to: 6.11
Change-Id: Id9219f6c00bd48d35d1d5c5b87eecb45f8c16c45
Reviewed-by: Mikko Hallamaa <mikko.hallamaa@qt.io>
Reviewed-by: Artem Dyomin <artem.dyomin@qt.io>
Reviewed-by: Elias Toivola <elias.toivola@qt.io>
(cherry picked from commit 75a537b6d5)
Reviewed-by: Qt Cherry-pick Bot <cherrypick_bot@qt-project.org>
The upstream vcpkg *-ohos triplets have been changed to build static
libraries in multi-config mode. Add (and use) an arm64-ohos-qt triplet
that builds shared libs in release mode.
The triplet differs from the upstream one only in the values
VCPKG_LIBRARY_LINKAGE and VCPKG_BUILD_TYPE.
This patch is a preparation for merging vcpkg upstream back to our
fork.
Change-Id: Iac6a4798b0322e9c57cf09ca35a408c66504ba46
Reviewed-by: Alexandru Croitor <alexandru.croitor@qt.io>
(cherry picked from commit 41986ce213)
Reviewed-by: Qt Cherry-pick Bot <cherrypick_bot@qt-project.org>
The Coin hosts file fully overrides the SDP default, which
had 127.0.0.1 and ::1 entries. Combined with nsswitch
"hosts: files mdnsd dns" and resolv.conf -> 172.31.1.1, any
test resolving http(s)://localhost fell through to NXDOMAIN.
Fixes tst_QHttpServer (229 HostNotFoundError asserts) and
tst_abstractoauth2 (silent crash) on QNX 8.0 QEMU. Applied
to 710/ too so the same latent issue can't surface there.
Pick-to: 6.11 6.8
Change-Id: I2aaa782980cb44afe3499ba8bd35fd7d3c093043
Reviewed-by: Simo Fält <simo.falt@qt.io>
Reviewed-by: Marianne Yrjänä <marianne.yrjana@qt.io>
(cherry picked from commit 00177db989)
Reviewed-by: Qt Cherry-pick Bot <cherrypick_bot@qt-project.org>
When HOME was unset, ~/.cache collapsed to /.cache on the read-only
QNX QEMU rootfs, so Fontconfig printed "No writable cache
directories" from QtGui-linking sub-tests and broke the
expected-output validation in tst_selftests.
Set HOME=/data/home/root (distinct from TMPDIR so filesystem
watcher tests keep separate watchable dirs) and point
FONTCONFIG_FILE at the deployed fonts.conf. QNX SDP 8.0 ships
fonts.conf at etc/fonts/fonts.conf, not etc/fontconfig/fonts.conf
as 7.1 did, so correct the data_files.custom source path too.
Squashes the former HOME-only and FONTCONFIG_FILE changes, which
conflicted on the same QNX_TEST_ENV lines and could not integrate
together.
Pick-to: 6.11 6.8
Change-Id: I1943d07eff0a2e99bb96db28e73b4c77e4aa2df8
Reviewed-by: Marianne Yrjänä <marianne.yrjana@qt.io>
Reviewed-by: Simo Fält <simo.falt@qt.io>
(cherry picked from commit 6282a3fd8a)
Reviewed-by: Qt Cherry-pick Bot <cherrypick_bot@qt-project.org>
And Packaging -flag moved from openSUSE 15.6
to a new openSUSE 16.0 [CI Platforms]
Pick-to: 6.11
Task-number: QTQAINFRA-7455
Task-number: QTQAINFRA-7452
Change-Id: I5726f5610fb3bde618e83468d1f9d3ed5083d51b
Reviewed-by: Simo Fält <simo.falt@qt.io>
(cherry picked from commit 393b7adc1f)
Reviewed-by: Qt Cherry-pick Bot <cherrypick_bot@qt-project.org>
We need to build it as no official pre-built binaries with
multiple targets exists of rust.
Pick-to: 6.11
Change-Id: Ibbe5dd77a92e845ce312f2ddf324a30b4c5ddc72
Reviewed-by: Simo Fält <simo.falt@qt.io>
(cherry picked from commit 01ed52ad4c)
Reviewed-by: Qt Cherry-pick Bot <cherrypick_bot@qt-project.org>
People might have other non-submodule directories in their Qt checkout,
e.g. ~/dev/qt/tasks, ~/qt/dev/research, ~/dev/qt/6.10, etc
We don't want to treat these as potential submodules.
Change-Id: I0765f1832e71fb541be3976810cd6b192fea17a2
Reviewed-by: Alexandru Croitor <alexandru.croitor@qt.io>
(cherry picked from commit 4826d56e8d)
Reviewed-by: Qt Cherry-pick Bot <cherrypick_bot@qt-project.org>
Rename windows-11-x86_64-arm64-tests to
windows-11-x86_64-arm64-native-tests and switch it from the host-side
cross-compile-tests flow to the native-build-tests flow:
* Features BuildTestsInTest + UseToolchainFromTargetDir build tests in
the test stage on the arm64 worker using the cross-built toolchain
(qtbase change 238400b22f3b327c05a51a913b279d4bf37f4adf).
* OpenSSL and FFmpeg env vars unblock qtnetwork and qtmultimedia.
Change-Id: Idd0565ceee0714d3f4fbe34ebf8d6373f7315cc1
Reviewed-by: Alexandru Croitor <alexandru.croitor@qt.io>
(cherry picked from commit 2b6e156008)
Reviewed-by: Qt Cherry-pick Bot <cherrypick_bot@qt-project.org>
vcpkg-tool release tag 2026-05-27 contains the patch necessary for
HarmonyOS support. We can use the unpatched upstream vcpkg-tool again.
Change the provisioning scripts back to fetch the tool from upstream's
release artifacts page.
Fixes: QTQAINFRA-7902
Change-Id: I84ef4582ef8ff5ca6e8e135128fe515438ac2a22
Reviewed-by: Elias Toivola <elias.toivola@qt.io>
Reviewed-by: Alexandru Croitor <alexandru.croitor@qt.io>
(cherry picked from commit 8d4971fd6e)
Reviewed-by: Qt Cherry-pick Bot <cherrypick_bot@qt-project.org>
Contains the .m2 folder from home after openapi build. Extracts it
to VM at same path.
Pick-to: 6.11
Change-Id: I3eb5858160db1c996f3c72fae2b91be1478f000c
Reviewed-by: Simo Fält <simo.falt@qt.io>
Reviewed-by: Elias Toivola <elias.toivola@qt.io>
(cherry picked from commit adc52dde71)
Reviewed-by: Qt Cherry-pick Bot <cherrypick_bot@qt-project.org>
To build / test Qt on a fresh VM, all provisioning scripts have to be
run.
Provide a shell script to facilitate this on Windows.
Fixes: QTQAINFRA-7906
Pick-to: 6.11 6.8
Change-Id: Ib06f75d7402f72e0496bab35aeb2ac89d1064537
Reviewed-by: Simo Fält <simo.falt@qt.io>
(cherry picked from commit 4f97b4bea8)
Reviewed-by: Qt Cherry-pick Bot <cherrypick_bot@qt-project.org>
To build / test Qt on a fresh VM, all provisioning scripts have to be
run.
Provide a shell script to facilitate this on Linux and macOS.
Fixes: QTQAINFRA-7906
Pick-to: 6.11 6.8
Change-Id: Ie06c11c824897d23c74d90c008a595c2f82f6950
Reviewed-by: Simo Fält <simo.falt@qt.io>
(cherry picked from commit c0e391423d)
Reviewed-by: Qt Cherry-pick Bot <cherrypick_bot@qt-project.org>
For scripted auto-execution all shell scripts in provisioning need to
be executbale. Most are, but some have been forgotten.
Make the remaining ones executable.
Fixes: QTQAINFRA-7905
Change-Id: I663aeb6c04f2b9d8049d21a75966369b15fe6d29
Reviewed-by: Simo Fält <simo.falt@qt.io>
(cherry picked from commit a377574e66)
Reviewed-by: Qt Cherry-pick Bot <cherrypick_bot@qt-project.org>
The rule in this form is not as helpful as intented.
Paraphrasing comments from the linked issue:
This rule was created based on clazy's “Warn when iterator objects are
implicitly cast to const_iterator" which was likely an attempt to limit
hidden detaches of implicitly-shared Qt containers.
But mixing const_iterator and iterator is not the problem. The problem
is calling a non-const begin()/end()/find()/etc when you only need
const_iterators. So if you ban the implicit conversion from iterator to
const_iterator, you will catch these, theoretically. Practically, no-one
writes QList<Foo>::const_iterator it = l.begin() these days anymore,
everyone is using auto, so the check can never actually trigger for True
Positives.
As-is, it produces False Positives which has a potential to make the
code actually worse.
An alternative to reach a similar goal is to use QT_STRICT_ITERATORS, so
there’s no need for an Axivion check for it.
Task-number: BAUHAUS-29596
Change-Id: I910e9ecc89c3db497c046f6d15ff07ab2ecc470a
Reviewed-by: Marc Mutz <marc.mutz@qt.io>
Reviewed-by: Volker Hilsheimer <volker.hilsheimer@qt.io>
(cherry picked from commit cc750dc924)
Reviewed-by: Qt Cherry-pick Bot <cherrypick_bot@qt-project.org>
