Provisioning openSuSE VMs with a populated /home/qt.cache creates
flaky crashes of plasmashell during KDE/Plasma startup.
This scrip wipes the directory at the end of provisioning
Pick-to: 6.4 6.3 6.2 5.15
Fixes: COIN-897
Change-Id: If61f86843e7b81dfee85610b1cd73bb15ce26658
Reviewed-by: Volker Hilsheimer <volker.hilsheimer@qt.io>
qtlocation is an ignored module, because it's not yet officially
supported in Qt 6. However, it is checked out when someone clones the
repo and wants to build Qt from sources.
The sha of the checked-out commit for qtlocation is very old, the repo
contains both qtlocation and qtpositioning sources at that revision.
It is causing configuration errors, because we now have qtpositioning in
its own repo, so we get duplicated targets.
This commit bumps the revision of qtlocation submodule to the current
dev HEAD. This will eliminate the configuration problems.
Change-Id: Ia5de4d1357ea657b42465e473d5b6e02a2bb6f30
Reviewed-by: Volker Hilsheimer <volker.hilsheimer@qt.io>
Ensure to explicitly use 8 cores for Android targets runnining
tests to reduce the amount of flaky fails due to the emulator
crashing or freezing.
Pick-to: 6.4 6.3 6.2
Task-number: COIN-896
Change-Id: I8b0cfac34aa7fc416166b9f7ae0b3e9d72c62e55
Reviewed-by: Alexandru Croitor <alexandru.croitor@qt.io>
Use the configure script to configure Qt in the CI, instead of calling
CMake directly.
Amends 21ed2db77b
Pick-to: 6.4
Task-number: QTQAINFRA-4357
Task-number: QTQAINFRA-4815
Change-Id: Ibd4ae9bb7dfdbff0cc1ae7803a6aaf5e0c504d2e
Reviewed-by: Toni Saario <toni.saario@qt.io>
Once these paths exist reliably on the Windows VM running the test, and
are shared, we can access them through UNC paths as
\\${COMPUTERNAME}\testshare
This allows us to remove dependencies to network infrastructure from
those QtCore tests.
The test needs to run last, as otherwise the Visual Studio installer
mysteriously fails to execute. So make some space at the end of the
script list.
Pick-to: 6.4
Change-Id: Ie11b894f000722a7d99b2c5e279c1b0b63021003
Reviewed-by: Simo Fält <simo.falt@qt.io>
Add flite install script for linux and integrate it in provisioning
for openSuSE Leap 15.3.
Pick-to: 6.4
Change-Id: Ie99271b115ba5c7b1f0177e09f38a4729de2b6cd
Reviewed-by: Volker Hilsheimer <volker.hilsheimer@qt.io>
The current cores count is 2 and that's leading to failures
in tests execution.
Pick-to: 6.4 6.3 6.2
Change-Id: Ia442c66f0c6246114f43f812240ad469dc705424
Reviewed-by: Jukka Jokiniva <jukka.jokiniva@qt.io>
The QNX build done on linux host can be used in installer for all host,
make sure that the wrapper scripts are also available for all hosts.
Pick-to: 6.4 6.3 6.2
Change-Id: I564b66682cdfd514e165dfb1542683e9a542a53d
Reviewed-by: Pasi Petäjäjärvi <pasi.petajajarvi@qt.io>
Faster, uses less memory, and has better debugging. Also needed to link
qtwebengine debug-builds on this arch.
Pick-to: 6.4
Change-Id: I337798a9191cb4a764de4b0251349e4e86b0288a
Reviewed-by: Alexandru Croitor <alexandru.croitor@qt.io>
This makes sure Android tests are run by default for packaging
targets for various integrations including qt5 integrations and
potential issues are caught up early on especially when doing
sumobules updates and coin scripts updates.
Also, this makes it easier to manage instead of having the tests
enabled per module. Thus, this removes the Android test include
from the individual modules because it will be retrieved directly
from cmake_platforms_target_android_host_linux.yaml which is included
by cmake_platforms.yaml.
Pick-to: 6.2 6.3 6.4
Task-number: QTBUG-88846
Change-Id: I8bc1638df48ad27781160df943c0126ffe495a3e
Reviewed-by: Toni Saario <toni.saario@qt.io>
This reverts commit 37fed2c22e.
Two new ASAN issues came up, disable ASAN build until they are fixed.
Change-Id: Id3815b891ec735d893375c02688383817d864719
Reviewed-by: Alexandru Croitor <alexandru.croitor@qt.io>
The last bugs have been fixed, and a test run built with ASAN is
not finding any issues on qtbase, so it is ready to be part of CI.
Fixes: QTQAINFRA-5025
Change-Id: I1905daaf5b19b41d8daa3f2c47958515b4afaded
Reviewed-by: Alexandru Croitor <alexandru.croitor@qt.io>
If the target does not match to the one used by qt5 it cannot find the
doc tar in the module doc build.
Change-Id: I1f3b86b72fb7c03c064ee1cbbd2d67653562c802
Reviewed-by: Jukka Jokiniva <jukka.jokiniva@qt.io>
Most of the modules do not have all configurations from different
yamls. Using configs from yamls only used in some modules will
lead to precheck using configs which are not used on normal
integrations.
Pick-to: 6.3 6.4
Change-Id: I7712db05eee485692d0363326194f02e21a40b9a
Reviewed-by: Alexandru Croitor <alexandru.croitor@qt.io>
When configuring with -libdir set to something that is not recognized
by CMake's find_package search procedure, top-level builds failed to
configure. This was due to a hard-coded lib/cmake directory added to
CMAKE_PREFIX_PATH.
Fixes: QTBUG-103823
Pick-to: 6.2 6.3 6.4
Change-Id: If8b48e35e654089f32cbe4af9936238cd82b3dbb
Reviewed-by: Alexandru Croitor <alexandru.croitor@qt.io>
SPDX-License-Identifier needs to stay on one line to be machine
readable, even if this goes above the 100 chars limit.
Pick-to: 6.4
Change-Id: I2cc3d556e30e8d169224cc87a97a2042b47e43f7
Reviewed-by: Mårten Nordheim <marten.nordheim@qt.io>
To ensure that both Linux and Windows host builds are equivalent
the Linux host builds need to use the common QNX SDP file that
support both host environments.
Task-number: QTBUG-101292
Pick-to: 6.4 6.3 6.2
Change-Id: Iaf3fe0de1bce64918165555bff07f5cb423fef32
Reviewed-by: Samuli Piippo <samuli.piippo@qt.io>
Add required configurations to Nightly run for building
Qt SW in Windows host for QNX OS.
Task-number: QTBUG-101292
Pick-to: 6.4 6.3 6.2
Change-Id: I689abd6596bf1ab1f30ba07c198e12569dbf2164
Reviewed-by: Heikki Halmet <heikki.halmet@qt.io>
The UseConfigure feature was enabled, but the configure arguments were
not ported.
Amends 5e9653ef97
Pick-to: 6.2 6.3 6.4
Task-number: QTQAINFRA-4357
Task-number: QTQAINFRA-4815
Change-Id: I89607aef275370dc27910a5cd1fec7603a1fd576
Reviewed-by: Alexey Edelev <alexey.edelev@qt.io>
Use the configure script to configure Qt in the CI, instead of calling
CMake directly.
Pick-to: 6.2 6.3 6.4
Task-number: QTQAINFRA-4357
Task-number: QTQAINFRA-4815
Change-Id: I9aacf3e6f15fc074b52e85da9e3f671b4f58a135
Reviewed-by: Alexey Edelev <alexey.edelev@qt.io>
One of the QtMultimedia backends is implemented using FFmpeg.
This provisioning enables building and testing of this backend.
Change-Id: Ia196c2ae4b457aa6b8e3ee8e0f367197aadfe0d9
Reviewed-by: Simo Fält <simo.falt@qt.io>
We already have the DownloadURL function which is used pretty
much everywhere except here, so it makes sense to use it here too.
Change-Id: Icc1d3db7e4e3d3f61f6cd6a22b35e2ef007ff40c
Reviewed-by: Tony Sarajärvi <tony.sarajarvi@qt.io>
Use the configure script to configure Qt in the CI, instead of calling
CMake directly.
Pick-to: 6.2 6.3 6.4
Task-number: QTQAINFRA-4357
Task-number: QTQAINFRA-4815
Change-Id: I2d35724074f4180775ca28c4befea1b9de838ecf
Reviewed-by: Alexey Edelev <alexey.edelev@qt.io>
Use the configure script to configure Qt in the CI, instead of calling
CMake directly.
Pick-to: 6.2 6.3 6.4
Task-number: QTQAINFRA-4357
Task-number: QTQAINFRA-4815
Change-Id: I128f5e424481ba8fbb4649c75be818abee57e03e
Reviewed-by: Alexey Edelev <alexey.edelev@qt.io>
Use the configure script to configure Qt in the CI, instead of calling
CMake directly.
Pick-to: 6.2 6.3 6.4
Task-number: QTQAINFRA-4357
Task-number: QTQAINFRA-4815
Change-Id: Ibb84a88f7f1ebd1f98e9998fac4180b257e80461
Reviewed-by: Alexey Edelev <alexey.edelev@qt.io>
Use the configure script to configure Qt in the CI, instead of calling
CMake directly.
Pick-to: 6.2 6.3 6.4
Task-number: QTQAINFRA-4357
Task-number: QTQAINFRA-4815
Change-Id: I534b630946f1fd9f79e8466886ea727697cabbc4
Reviewed-by: Alexey Edelev <alexey.edelev@qt.io>
Use the configure script to configure Qt in the CI, instead of calling
CMake directly.
Pick-to: 6.2 6.3 6.4
Task-number: QTQAINFRA-4357
Task-number: QTQAINFRA-4815
Change-Id: I6fa9d75fab32f7355847a09996876f7e6c0a8b1c
Reviewed-by: Alexey Edelev <alexey.edelev@qt.io>
Use the configure script to configure Qt in the CI, instead of calling
CMake directly.
Pick-to: 6.2 6.3 6.4
Task-number: QTQAINFRA-4357
Task-number: QTQAINFRA-4815
Change-Id: I008dd8dfca800e94ea3448bfd2c7ebae3266983e
Reviewed-by: Alexey Edelev <alexey.edelev@qt.io>
Use the configure script to configure Qt in the CI, instead of calling
CMake directly.
As a drive-by, remove the qt tiff option from qtbase configure args.
The feature is only available in qtimageformats.
Amends a97bdde4d4 and
4b4f0be08d
Also remove redundant compiler launcher assignments.
Pick-to: 6.2 6.3 6.4
Task-number: QTQAINFRA-4357
Task-number: QTQAINFRA-4815
Change-Id: I5cfcf5ddf60e9dd77cb67f41bb75525b44ad78d3
Reviewed-by: Alexey Edelev <alexey.edelev@qt.io>
Use the configure script to configure Qt in the CI, instead of calling
CMake directly.
As a drive-by, remove the qt tiff option from qtbase configure args.
The feature is only available in qtimageformats.
Amends a97bdde4d4 and
4b4f0be08d
Pick-to: 6.2 6.3 6.4
Task-number: QTQAINFRA-4357
Task-number: QTQAINFRA-4815
Change-Id: I722bd869315b9059f5cadc5e935ed5173edf370d
Reviewed-by: Alexey Edelev <alexey.edelev@qt.io>
Use the configure script to configure Qt in the CI, instead of calling
CMake directly.
As a drive-by, remove compiler launcher assignments. They are
handled automatically by the qtbase instructions.
Pick-to: 6.2 6.3 6.4
Task-number: QTQAINFRA-4357
Task-number: QTQAINFRA-4815
Change-Id: Id7b02804aa2c931e81f227cae64b19ab0e40f82d
Reviewed-by: Alexey Edelev <alexey.edelev@qt.io>
Use the configure script to configure Qt in the CI, instead of calling
CMake directly.
Pick-to: 6.2 6.3 6.4
Task-number: QTQAINFRA-4357
Task-number: QTQAINFRA-4815
Change-Id: I153b9268f8795c33a44f85a316fa7c1c31ac0492
Reviewed-by: Alexey Edelev <alexey.edelev@qt.io>
Use the configure script to configure Qt in the CI, instead of calling
CMake directly.
Pick-to: 6.2 6.3 6.4
Task-number: QTQAINFRA-4357
Task-number: QTQAINFRA-4815
Change-Id: I1fef5b57c493d1e32080fad393e4e531e441e142
Reviewed-by: Alexey Edelev <alexey.edelev@qt.io>
Use the configure script to configure Qt in the CI, instead of calling
CMake directly.
Pick-to: 6.2 6.3 6.4
Task-number: QTQAINFRA-4357
Task-number: QTQAINFRA-4815
Change-Id: If84d580bdcf166f07ecd1f6fb20e3404e1fb0e1c
Reviewed-by: Alexey Edelev <alexey.edelev@qt.io>
Use the configure script to configure Qt in the CI, instead of calling
CMake directly.
Pick-to: 6.2 6.3 6.4
Task-number: QTQAINFRA-4357
Task-number: QTQAINFRA-4815
Change-Id: I38e038e6682f77a5ea3f2335f24f8bcbd2e7c605
Reviewed-by: Alexey Edelev <alexey.edelev@qt.io>
Use the configure script to configure Qt in the CI, instead of calling
CMake directly.
Pick-to: 6.2 6.3 6.4
Task-number: QTQAINFRA-4357
Task-number: QTQAINFRA-4815
Change-Id: Ia2461f24ba526702196f72ea492b59cc2b1abf5a
Reviewed-by: Alexey Edelev <alexey.edelev@qt.io>
Use the configure script to configure Qt in the CI, instead of calling
CMake directly.
Pick-to: 6.2 6.3 6.4
Task-number: QTQAINFRA-4357
Task-number: QTQAINFRA-4815
Change-Id: I2620014c3858c1f343f8698fc3f8de4f9188ad4b
Reviewed-by: Alexey Edelev <alexey.edelev@qt.io>
