We don't use this anywhere except when running tests in COIN,
so this is wasted time & resources.
Change-Id: Ied053e0ffcdf41b460cda6f093b7c85143e53d6f
Reviewed-by: Simo Fält <simo.falt@qt.io>
Larger archives seem to result in upload issues.
Change-Id: Id73bf203c609f07ad1174839e3ada0049416a66d
Reviewed-by: Qt CI Bot <qt_ci_bot@qt-project.org>
Reviewed-by: Simo Fält <simo.falt@qt.io>
Some of our auto tests fail, so add an EXCLUDE_FROM_PRECHECK option for
add_qtc_test, which sets a corresponding label on the ctest, and exclude
these when running ctest on COIN.
Disable the Googletest based unittests for now, they are inconsistently
failing on CI, e.g. sometimes timing out after 60 seconds for tests that
usually take only a fraction of a second.
tst_perfdata from the perfparser submodule also fails. Temporarily
disable it explicitly, until the EXCLUDE_FROM_PRECHECK change can be
merged there.
Change-Id: I7e9d7aded75bbe8800f82f7aa125c181271a2a1f
Reviewed-by: Qt CI Bot <qt_ci_bot@qt-project.org>
Reviewed-by: Jarek Kobus <jaroslaw.kobus@qt.io>
Reviewed-by: <github-actions-qt-creator@cristianadam.eu>
For now just run them without failing the precheck on failing tests.
The test results are only visible in the precheck details
on testresults.qt.io
Remove the fixed timeout of 5 seconds, since this depends on the test
setup where the tests are run, and it is not possible to override a
fixed timeout with the --timeout option of ctest.
Change-Id: Ib5f12092b64d0cf87e1213b031e1990973e18669
Reviewed-by: Cristian Adam <cristian.adam@qt.io>
Reviewed-by: Qt CI Bot <qt_ci_bot@qt-project.org>
Reviewed-by: <github-actions-qt-creator@cristianadam.eu>
To be in sync with the official packaging.
Change-Id: I28712ad1e8234d4911b2afcce949e1e919bf8e92
Reviewed-by: Eike Ziller <eike.ziller@qt.io>
Reviewed-by: Qt CI Bot <qt_ci_bot@qt-project.org>
Explicitly use Python3 for the scripts
The install_qt script was ported to Python3, and we now need to
explicitly state python3 as the interpreter.
Change-Id: If0d94fde127868ac024834f5f6eccecd1bbc0e6e
Reviewed-by: Qt CI Bot <qt_ci_bot@qt-project.org>
Reviewed-by: Iikka Eklund <iikka.eklund@qt.io>
Since we still support Qt 5 based builds, it is good to have it in
the precheck.
Change-Id: Iba58c9ac0c49fa87bf020e7dceef25f87c9aa454
Reviewed-by: <github-actions-qt-creator@cristianadam.eu>
Reviewed-by: Antti Kokko <antti.kokko@qt.io>
It is not qt5 anymore, and the version number is not needed anyhow
Change-Id: I68d53547ce902225bd0d596457a583c5768a8e94
Reviewed-by: Qt CI Bot <qt_ci_bot@qt-project.org>
Reviewed-by: David Schulz <david.schulz@qt.io>
In order to enable tools like qmllint and in order to avoid the
following warning, define QT_QML_OUTPUT_DIRECTORY
Warning message:
The Tracing target is a QML module with target path QtCreator/FooBar.
It uses an OUTPUT_DIRECTORY of foobar, which should end in the same
target path, but doesn't. Tooling such as qmllint may not work
correctly.
Since this change is relevant for the build against Qt 6.2-Beta4,
common_environment.yaml gets bumped, accordingly.
Change-Id: Ic6766cf29baddd7c22b68270a0f1702aade7c53f
Reviewed-by: Eike Ziller <eike.ziller@qt.io>
This change fixes the failing configuration against a recent Qt (post
6.2-Beta2) build:
CMake Error at QTDIR/qtbase/lib/cmake/Qt6Qml/Qt6QmlMacros.cmake:196
(message):
PLUGIN_TARGET must also be provided when NO_CREATE_PLUGIN_TARGET is
used.
If you want to disable creating a plugin altogether, use the NO_PLUGIN
option instead.
Change-Id: If1dbfb09bda8e8cdd07cc575076dd6ccec1a4d39
Reviewed-by: Ulf Hermann <ulf.hermann@qt.io>
It is a stable base to run the precheck on.
Change-Id: Ie5e0699b9067dccba85a3ad4e1b9102799ca5d0f
Reviewed-by: Qt CI Bot <qt_ci_bot@qt-project.org>
Reviewed-by: Eike Ziller <eike.ziller@qt.io>
We are passing it explicitly to the build script and don't use the
provisioned version anyhow.
Change-Id: Id136e06023621389763eeeda021fa64551a148a3
Reviewed-by: Antti Kokko <antti.kokko@qt.io>
There is some fancy logic in COIN that sets different number of
CPUs depending on configuration, which lead to our Linux machines
crawling, while macOS and Windows at least got 4 CPUs.
Fix (and increase) the number of CPUs for all platforms.
Change-Id: I3191f1645420805f5899af8966fd1d377a89bf85
Reviewed-by: Cristian Adam <cristian.adam@qt.io>
Was missing for some.
Change-Id: I53aad1dbe352ed62c0c41376771c961aeca960e9
Reviewed-by: Qt CI Bot <qt_ci_bot@qt-project.org>
Reviewed-by: Cristian Adam <cristian.adam@qt.io>
Not needed for pre-checks and takes a considerable amount of time.
Change-Id: I2ab7d51bd75cfbafd5f7dd696f73740b9be035bb
Reviewed-by: Qt CI Bot <qt_ci_bot@qt-project.org>
Reviewed-by: Cristian Adam <cristian.adam@qt.io>
sccache does not support the "/Zi /FS" option for debug information
with MSVC. Optionally replace "/Zi" by "/Z7", which leaves debug
information in the object files and only collects it at link time.
See also qtbase 2354274f39934b94383923834479901106489def.
Change-Id: Id94c2116f3c4192556dbdf8fe82b12ce0a204273
Reviewed-by: Qt CI Bot <qt_ci_bot@qt-project.org>
Reviewed-by: Cristian Adam <cristian.adam@qt.io>
It is already done together with install_qt.py
Change-Id: I17d7e1293dec42f8c8dc6be9105236690ba417cd
Reviewed-by: Qt CI Bot <qt_ci_bot@qt-project.org>
Reviewed-by: Matti Paaso <matti.paaso@qt.io>
Unfortunately we have to turn off separate debug info for this,
because sccache is not compatible with /Zi on Windows.
Change-Id: I5e9e3bb298bd4f72a79e944485523a553349590b
Reviewed-by: Qt CI Bot <qt_ci_bot@qt-project.org>
Reviewed-by: Cristian Adam <cristian.adam@qt.io>
Use the new, simpler install_qt command and centralize definition
of Qt base URL and modules
Change-Id: I73d0b195c0cb6278d4f79476c42a39446d43eaed
Reviewed-by: Qt CI Bot <qt_ci_bot@qt-project.org>
Reviewed-by: Matti Paaso <matti.paaso@qt.io>
