Debian is no longer supported for Qt 6.8.1 and later
Pick-to: 6.9 6.8
Change-Id: Ic9ddac3d95451b900f60be6a90efd5fb32985601
Reviewed-by: Patrik Teivonen <patrik.teivonen@qt.io>
Reviewed-by: David Schulz <david.schulz@qt.io>
That is what we are using for packages too.
Pick-to: 6.8 6.9
Change-Id: I88ab02f577933292c882ec4633d9087b1bf957ea
Reviewed-by: Tero Heikkinen <tero.heikkinen@qt.io>
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.
Pick-to: 6.9
Task-number: QTQAINFRA-6702
Change-Id: I001fc2d3740a287d4546d0f597e81ded9f5449cb
Reviewed-by: Jukka Jokiniva <jukka.jokiniva@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.9 6.8
Change-Id: I3bc5c8bb63abbb729d03fcf3afb2f7881bcdd270
Reviewed-by: Simo Fält <simo.falt@qt.io>
Id: 'macos-13-arm-on-arm64-tests' was just removed, adjust
qtsaferenderer-runtime.yaml configuration to match
what's defined in macos.yaml.
Keep feature definitions same than before for
added 'macos-13-arm64-tests'.
Change-Id: I97becead1e7155d4d586692fd6ff87fad636efd3
Reviewed-by: Teemu Holappa <teemu.holappa@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.9 6.8
Change-Id: I40aa3c1852fb0baf3366fa1a9dab85a66eef95e2
Reviewed-by: Joerg Bornemann <joerg.bornemann@qt.io>
Reviewed-by: Alexandru Croitor <alexandru.croitor@qt.io>
Axivion analysis for qt5 started to fail at out of memory.
Increasing virtual machine size to correct the problem.
Task-number: QTQAINFRA-6931
Change-Id: I2d0f1ee655a1449926f9938dbae6f4be0afbce8f
Reviewed-by: Toni Saario <toni.saario@qt.io>
Newer version of Chrome together with healdess mode
should provide more stability.
Pick-to: 6.9
Change-Id: Ifb6b326b90067d9e069ebef662356d28e2c9edd7
Reviewed-by: Morten Johan Sørvig <morten.sorvig@qt.io>
By removing the InsignificantTests flag and adding the
COIN_CTEST_IGNORE_EXIT_CODE env var we can control the
significance at the module level.
Change-Id: I89171f6dbed8c38aed279aec01e3bad36a157f5e
Reviewed-by: Joerg Bornemann <joerg.bornemann@qt.io>
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.9 6.8 6.5
Change-Id: Icb6de43f3e2c2f7f98f3172c83d66bebf9603d24
Reviewed-by: Assam Boudjelthia <assam.boudjelthia@qt.io>
WoA template got updated in 2151c5510f
and 0f18b0bc2f, but not everywhere.
Pick-to: 6.9 6.8
Change-Id: Ie2ee9e62f9bc10753bd527a2b1a7edc5de46ca60
Reviewed-by: Tero Heikkinen <tero.heikkinen@qt.io>
Reviewed-by: Simo Fält <simo.falt@qt.io>
Change Windows 22h2 arm64 tier-1 template -54 -> -55, where Windows
SDK 10.0.26100.1742 is installed.
Task-number: COIN-1206
Change-Id: Id4b008d12ee092daa1e84c50d9a36240ee680483
Reviewed-by: Michal Klocek <michal.klocek@qt.io>
Change Windows 10 22h2 x86_64 tier-1 template -52 -> -53, where Windows
SDK 10.0.26100.1742 is installed.
Task-number: COIN-1206
Change-Id: Ia78f8d3b67c3aa546a4f47ad503f44782722631f
Reviewed-by: Michal Klocek <michal.klocek@qt.io>
Change Windows 11 23h2 x86_64 tier-1 template -53 -> -54, where Windows SDK 10.0.26100.1742 is installed.
Task-number: COIN-1206
Change-Id: I713ea4d5032145a92d7bcbccec6c98543cbc90d2
Reviewed-by: Michal Klocek <michal.klocek@qt.io>
CI configs for new Boot2Qt repo.
Task-number: QTBUG-127698
Change-Id: I26fcc8c6a2224959a670290f7fcfe402ed7be137
Reviewed-by: Tero Heikkinen <tero.heikkinen@qt.io>
Reviewed-by: Heikki Halmet <heikki.halmet@qt.io>
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
Pick-to: 6.9
Change-Id: I175ce8459660465477a0ac29d65353c871df69b9
Reviewed-by: Toni Saario <toni.saario@qt.io>
This makes ARM target tests significant for qtbase, qtgraphs and
qtgrpc. Intel target tests for qtgraphs, qtgrpc, qtlanguageserver,
qtquicktimeline, qtmultimedia, qtshadertools and qtsvg.
Pick-to: 6.9
Change-Id: I4ae3591dacb21207d5aaf65c1fdff4fd19c3903c
Reviewed-by: Tero Heikkinen <tero.heikkinen@qt.io>
Reviewed-by: Simo Fält <simo.falt@qt.io>
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
Pick-to: 6.9
Change-Id: I34f76b127899a878ef2ddf8f3c09904d8e21f493
Reviewed-by: Heikki Halmet <heikki.halmet@qt.io>
We want automated testing for QtGP. Test cases that can be run with
Gradle have been made a while ago, but they were only run locally by the
developers.
This commit adds Linux/macOS/Windows configurations for QtGP. These are
marked TestOnly as the build/test process in Gradle is packaged together
and we don't want to initiate builds for the Qt side.
Task-number: QTTA-217
Change-Id: I777d191596f43089d0ad80cbb6470c62a0eee257
Reviewed-by: Assam Boudjelthia <assam.boudjelthia@qt.io>
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>
-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>
Qt auto tests now require exceptions due to usage of
QTEST_THROW_ON_FAIL and QTEST_THROW_ON_SKIP.
Task-number: QTBUG-121822
Change-Id: I755752c6324368c5cd2509216ec6bb0a3090896c
Reviewed-by: Lorn Potter <lorn.potter@qt.io>
Wrong emulator is started because of this and none of tests run.
Change-Id: I47fee8d69feadccfdd8b5c27e7ff63df550352fa
Reviewed-by: Simo Fält <simo.falt@qt.io>
Both modules are using their own features to enable coco
instructions.
Task-number: QSR-2578
Change-Id: I64ba6a372f19a8f980e2e620786f10c8345f3e5b
Reviewed-by: Toni Saario <toni.saario@qt.io>
To get as close as possible to how developers build and run
tests, and to get debug-build test coverage on macOS in CI.
Pick-to: 6.8
Change-Id: Ice12b7230d56284d352e6a73ac503588b22107bb
Reviewed-by: Joerg Bornemann <joerg.bornemann@qt.io>
Reviewed-by: Alexey Edelev <alexey.edelev@qt.io>
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.
Task-number: QTQAINFRA-6702
Change-Id: Ie0abd68e0ce80008776f3d0fe931d996f6eb3a61
Reviewed-by: Jukka Jokiniva <jukka.jokiniva@qt.io>
