Qt Wayland client was moved into qtbase. We will try to enable
them from qtbase to all modules in the future in dev. For 6.9
and 6.8, they are InsignificantTests, waste some CI resources.
Perhaps we can fix them later, but I don't think it's worthy.
Pick-to: 6.8
Change-Id: I0f26312284bec4f02da915e829d3a68aac820ceb
Reviewed-by: Tor Arne Vestbø <tor.arne.vestbo@qt.io>
(cherry picked from commit 57340da291)
Reviewed-by: Qt Cherry-pick Bot <cherrypick_bot@qt-project.org>
(cherry picked from commit 28335a188b)
We used to build the documentation with these configurations but they
changed to developer-builds and the documentation was moved to a
separate configurations (documentation-warnings, offline-documentation).
We added those configurations but ignored the developer-builds, and at
the moment they are not doing anything expect wasting resources when
acquiring VMs, so let's get rid of them.
Fixes: QAA-2976
Change-Id: Ia9509e43aec2974bae098de8a2d13ac9d29e2fad
Reviewed-by: Petri Virkkunen <petri.virkkunen@qt.io>
(cherry picked from commit aae8dc578b)
Reviewed-by: Qt Cherry-pick Bot <cherrypick_bot@qt-project.org>
(cherry picked from commit 9c6e9e26c4)
Change is done in Tier 1 image:
qtci-linux-SLES-15_SP6-x86_64-52
Task-number: QTBUG-136467
Change-Id: I2924f3250dbe914b0c6bc687241725175d5f7aa5
Reviewed-by: Jukka Jokiniva <jukka.jokiniva@qt.io>
(cherry picked from commit 45ffa61110)
Reviewed-by: Axel Spoerl <axel.spoerl@qt.io>
They frequently fail tests. Since 6.9 is not an LTS branch, we can
ignore test failures for this platform.
Change-Id: I2e69bd9b123937366e73c1f30e063494f43a6ca7
Reviewed-by: <lazo.eric@qt.io>
Reviewed-by: Jani Heikkinen <jani.heikkinen@qt.io>
Reviewed-by: Axel Spoerl <axel.spoerl@qt.io>
Reviewed-by: Jarno Lämsä <jarno.lamsa@qt.io>
Starting from 6.9 the "ubuntu-22.04-documentation-x11-tests" config
was replaced by "ubuntu-22.04-developer-build-x11-tests". The new
configuration doesn't test the documentation for warnings which is
why we had failures in 6.8 where to docs were checked but not in 6.9
or dev.
This commit fixes the issue by adding the relatively new
"documentation-warnings" configuration, which will once again check
our documentation.
See also 434e4a224a .
Task-number: QAA-2878
Pick-to: 6.9.0
Change-Id: I479a9606ab16f8b87009d26ab03636c4c658fcb5
Reviewed-by: Liang Qi <liang.qi@qt.io>
Reviewed-by: Jukka Jokiniva <jukka.jokiniva@qt.io>
(cherry picked from commit ea1abd55ce)
Reviewed-by: Assam Boudjelthia <assam.boudjelthia@qt.io>
Previous dependency platform had been removed from CI, leading nightly
builds failing silently. Changed also from MSCV to mingw since it seems
to be more commonly used among customers.
Task-number: QTQAINFRA-7017
Task-number: QTQAINFRA-7000
Pick-to: 6.8
Change-Id: I009dd5e5c5ad28434816f831de37849a53f2c24f
Reviewed-by: Jukka Jokiniva <jukka.jokiniva@qt.io>
Reviewed-by: Tero Heikkinen <tero.heikkinen@qt.io>
(cherry picked from commit c47f750e65)
Reviewed-by: Qt Cherry-pick Bot <cherrypick_bot@qt-project.org>
In practice it already is, because qtbase sets COIN_CTEST_IGNORE_EXIT_CODE
to 0 for macOS 15, and this change has propagated to qt5.git now, but this
makes it official.
macOS 15 is now a significant platform [CI Platforms]
Change-Id: I9dc8b0f56582e08560859a17304e886e7fc3020b
Reviewed-by: Jukka Jokiniva <jukka.jokiniva@qt.io>
(cherry picked from commit 7853bee060)
Reviewed-by: Ville-Pekka Karhu <ville-pekka.karhu@qt.io>
QNX qemu configs separated. QNX710 and QNX800 require different set of
dependency libraries and there's an extra image creation bug on QNX800
that needs workaround too.
QNX800 toolchain updated.
Task-number: QTBUG-131708
Pick-to: 6.8
Change-Id: I3bc5c8bb63abbb729d03fcf3afb2f7881bcdd270
Reviewed-by: Simo Fält <simo.falt@qt.io>
(cherry picked from commit 4791054b10)
Reviewed-by: Qt Cherry-pick Bot <cherrypick_bot@qt-project.org>
Debian is no longer supported for Qt 6.8.1 and later
Pick-to: 6.8
Change-Id: Ic9ddac3d95451b900f60be6a90efd5fb32985601
Reviewed-by: Patrik Teivonen <patrik.teivonen@qt.io>
Reviewed-by: David Schulz <david.schulz@qt.io>
(cherry picked from commit 014bdc24ab)
Reviewed-by: Qt Cherry-pick Bot <cherrypick_bot@qt-project.org>
That is what we are using for packages too.
Pick-to: 6.8
Change-Id: I88ab02f577933292c882ec4633d9087b1bf957ea
Reviewed-by: Tero Heikkinen <tero.heikkinen@qt.io>
(cherry picked from commit 53280b0697)
Reviewed-by: Qt Cherry-pick Bot <cherrypick_bot@qt-project.org>
Effect of this experiment was inconclusive. In some isolated cases
limited benefit was seen, but in overall metrics no change was
observed.
Remove the feature to gain the lost computing capacity back. If the
removal causes noticeably higher flakiness etc, it can be reevaluated.
Task-number: QTQAINFRA-6702
Change-Id: I001fc2d3740a287d4546d0f597e81ded9f5449cb
(cherry picked from commit 8d51e875cb)
Reviewed-by: Jukka Jokiniva <jukka.jokiniva@qt.io>
The hard-coded path paths added to LIBRARY_PATH and CPLUS_INCLUDE_PATH
was not correct on Apple Silicon Macs, where homebrew installs into
/opt/homebrew/.
There's also no point in passing on the library location via compiler
environment variables, when we can use ODBC_ROOT. And we don't need
to pass it on as a CMake define, as a environment variable works just
fine. This decouples the provisioning of libiodbc from the build
configurations.
Pick-to: 6.8
Change-Id: I40aa3c1852fb0baf3366fa1a9dab85a66eef95e2
Reviewed-by: Joerg Bornemann <joerg.bornemann@qt.io>
Reviewed-by: Alexandru Croitor <alexandru.croitor@qt.io>
(cherry picked from commit 124957a8cb)
Reviewed-by: Qt Cherry-pick Bot <cherrypick_bot@qt-project.org>
Newer version of Chrome together with healdess mode
should provide more stability.
Change-Id: Ifb6b326b90067d9e069ebef662356d28e2c9edd7
Reviewed-by: Morten Johan Sørvig <morten.sorvig@qt.io>
(cherry picked from commit ae85de3cf8)
Reviewed-by: Qt Cherry-pick Bot <cherrypick_bot@qt-project.org>
This patch
- Replaces Android 14 with Android 15 as a maximum version
- Introduces Android 15 system image to CI cache
- Sets Android 15 as significant
Task-number: QTQAINFRA-6478
Fixes: QTQAINFRA-6652
Pick-to: 6.8 6.5
Change-Id: Icb6de43f3e2c2f7f98f3172c83d66bebf9603d24
Reviewed-by: Assam Boudjelthia <assam.boudjelthia@qt.io>
(cherry picked from commit 2c85a91e07)
Reviewed-by: Qt Cherry-pick Bot <cherrypick_bot@qt-project.org>
This will use the newer iOS 17 SDK during the build, and allow us to
enforce the minimum SDK version check.
This change also switches to using an arm mac for the build.
Pick-to: 6.8
Task-number: QTBUG-119490
Change-Id: Ie9ff2b2f4fe40bda2856d4b12a03aaa05f836de4
Reviewed-by: Tor Arne Vestbø <tor.arne.vestbo@qt.io>
(cherry picked from commit f5970f9c62)
Reviewed-by: Qt Cherry-pick Bot <cherrypick_bot@qt-project.org>
Qt auto tests now require exceptions due to usage of
QTEST_THROW_ON_FAIL and QTEST_THROW_ON_SKIP.
(Amends 72e2341971)
Task-number: QTBUG-121822
Change-Id: I175ce8459660465477a0ac29d65353c871df69b9
Reviewed-by: Toni Saario <toni.saario@qt.io>
(cherry picked from commit 565847e632)
Reviewed-by: Qt Cherry-pick Bot <cherrypick_bot@qt-project.org>
This makes ARM target tests significant for qtbase, qtgraphs and
qtgrpc. Intel target tests for qtgraphs, qtgrpc, qtlanguageserver,
qtquicktimeline, qtmultimedia, qtshadertools and qtsvg.
Change-Id: I4ae3591dacb21207d5aaf65c1fdff4fd19c3903c
Reviewed-by: Tero Heikkinen <tero.heikkinen@qt.io>
Reviewed-by: Simo Fält <simo.falt@qt.io>
(cherry picked from commit 90071f1d7c)
Reviewed-by: Qt Cherry-pick Bot <cherrypick_bot@qt-project.org>
Extending feature usage with newest and recently added CI platforms
- openSUSE 15.6
- SLES 15 SP6
The feature enables 1:1 pinning of CPU cores for VM, which should mean
more stable CPU allocation from host and fewer sporadic failure.
The down side of this is that the targets will effectively use double
the capacity from the host that they previously would. It is to be seen
how effective this is in reducing flakiness, which would counter the
increased usage by reducing staging needed.
In Coin the feature is limited so that it only affects test VMs.
(Amends cf237ca8dc)
Task-number: QTQAINFRA-6702
Change-Id: I34f76b127899a878ef2ddf8f3c09904d8e21f493
Reviewed-by: Heikki Halmet <heikki.halmet@qt.io>
(cherry picked from commit 1c4e0928ff)
Reviewed-by: Qt Cherry-pick Bot <cherrypick_bot@qt-project.org>
-no-feature-exceptions is now possible.
+ more disabled features
Task-number: QTBUG-122999
Change-Id: Ia0a90c62996239d437c39546302cc252529f5655
Reviewed-by: Samuli Piippo <samuli.piippo@qt.io>
Amends c5ab2fe4fa
Option -force-asserts need to be added also to
-debug-and-release configurations.
Task-number: QTQAINFRA-6624
Change-Id: If98c9e477cc7f788bbaf265e7a8a2fc8baba5465
Reviewed-by: Tero Heikkinen <tero.heikkinen@qt.io>
Reviewed-by: Toni Saario <toni.saario@qt.io>
SLES 15 SP6 and Opensuse 15.6 seem to need direct configuration
for git and curl to take CA certificates into use. [CI Platforms]
nodejs18:
- Needed for QtWebEngine build done in RTA
- But nodejs18 doesn't yet have a provider
- Therefore using commonly installed nodejs 18.6.0 as it's available
Task-number: QTQAINFRA-6746
Task-number: QTQAINFRA-6745
Change-Id: I73fb2a98a648f56b7330e26811e6d4780c51ab80
Reviewed-by: Heikki Halmet <heikki.halmet@qt.io>
This is to run full set of tests instead of stopping of first error.
Change-Id: I606415b6a94f0b8a4a578cce4c4b8f4cce01479a
Reviewed-by: Matti Paaso <matti.paaso@qt.io>
OpenSUSE 15.6 and SLES 15 SP6 seem to need direct configuration
for git and curl to take CA certificates into use. [CI Platforms]
Includes fix to install gstreamer h264 codec
(amending 58e0090020)
Task-number: QTQAINFRA-6740
Task-number: QTQAINFRA-6739
Change-Id: I0d92ef50527564d2f048174777e20d1611aaf4d2
Reviewed-by: Axel Spoerl <axel.spoerl@qt.io>
Enable test building for all modules VxWorks is to be ported to.
Set modules that fail as insignificant. Keep x86_64 target as
insignificantTests, due to it requiring change in qtbase, after
which it can be default significant.
Change-Id: I3c373a2a548c71515901c180e299738f5326c8a4
Reviewed-by: Jukka Jokiniva <jukka.jokiniva@qt.io>
The documentation warning configurations marked with the TestDocs
feature will now use the new doc tools building instructions from
qtbase, instead of using the provisioned qdoc tools when checking the
documentation for warnings.
This means that each qtbase integration will build the doc tools
from qttools/dev/HEAD and use those built tools associated with that
qtbase sha1 integration to check documentation in all other
repositories.
The doc tools will be rebuilt whenever a new qtbase integration
starts.
See the qtbase commit 1f646bb978ed94c25f6224e801779c929096c0ae for
more details.
Task-number: QTBUG-128730
Change-Id: I5a981afa9ec2c2b3a5c519b961e566ec5d2cc925
Reviewed-by: Alexey Edelev <alexey.edelev@qt.io>
