For the regular checks we should be as fast as possible.
Change-Id: If5b14f6ac48aebdefced137f74fc8ecdd72f741b
Reviewed-by: Eike Ziller <eike.ziller@qt.io>
- use the release tag for the artifact name instead of github.run_id
- add releases notes to the github release page
- enable macos universal builds
- add architecture in the artifact name
Change-Id: I478d2fb677b60fb2e59c154d538af94d1fddfac5
Reviewed-by: Eike Ziller <eike.ziller@qt.io>
This removes the warnings that the jobs display due to upgrades
that will be done for the internal GitHub Actions services.
Change-Id: I4865c7e61f3da04a00f14657a87ecdd63c24325c
Reviewed-by: <github-actions-qt-creator@cristianadam.eu>
Reviewed-by: Eike Ziller <eike.ziller@qt.io>
Also change to MSVC 2022, which is the only MSVC compiler present
on the windows-latest runner.
MSVC 2022 is backwards compatible with MSVC 2019 and should work
fine with our Qt 6.3.1 MSVC 2019 package.
Change-Id: Id9967de33d2fea03f86243f8d54d369095918cfe
Reviewed-by: <github-actions-qt-creator@cristianadam.eu>
Reviewed-by: Eike Ziller <eike.ziller@qt.io>
Also increase timeout to 300s.
Currently only the Linux runner is running the docker test,
and building on Linux is usually the fastest. Should not
affect the overall job time.
Change-Id: Ie7aa72da1ffac987ef732ad0fb8076d473d00185
Reviewed-by: Eike Ziller <eike.ziller@qt.io>
Reviewed-by: <github-actions-qt-creator@cristianadam.eu>
As done for the Windows configuration. macOS comes automagically with
a software renderer.
Change-Id: Ifa64fc80f9ce69b87fb589675e794ac3b537cc48
Reviewed-by: Eike Ziller <eike.ziller@qt.io>
Since some tests are failing due to missing OpenGL context, I assume
the GitHub Actions Windows runners do not have OpenGL drivers.
Change-Id: I7951f0906d37bc1d513e77540fdd379a71cbed60
Reviewed-by: <github-actions-qt-creator@cristianadam.eu>
Reviewed-by: Eike Ziller <eike.ziller@qt.io>
The precheck tests have only a few cases which should not block the
runners anymore.
Change-Id: I00bea0d208aa646dbdb4c146f46fdb853bc8aa5b
Reviewed-by: <github-actions-qt-creator@cristianadam.eu>
Reviewed-by: Eike Ziller <eike.ziller@qt.io>
Add a pull request template to inform the potential contributor that the
github Qt Creator presence a mirror is, and that the only way to
contribuite is through gerrit.
Change-Id: I5ddc93f182aaaa87e465677a28705ac5efa04f7f
Reviewed-by: Eike Ziller <eike.ziller@qt.io>
Reviewed-by: Alessandro Portale <alessandro.portale@qt.io>
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>
Both LLVM/Clang 14.0 and Qt 6.2.3 dependencies have been compiled
with MinGW 11.2.0
Change-Id: I14dc8b62d243f21dc31ba72605d5aa4b16085279
Reviewed-by: <github-actions-qt-creator@cristianadam.eu>
Reviewed-by: Eike Ziller <eike.ziller@qt.io>
windows-latest is "transitioning to 2022" currently, and that seems to
mean that for some users this is already 2022 and for some still 2019.
Explicitly state something.
Change-Id: I1e7ba6fa60b9fe44c78505b322ff8278c2e41ee6
Reviewed-by: Alessandro Portale <alessandro.portale@qt.io>
Currently the macOS job runner is failing sporadically and since the
tests are only 99% passing and they are only informative only if the
developer actively checks a test in the output log.
Change-Id: Id75d8d05c5fd45f2cc15e08b20973646a06ff6bd
Reviewed-by: <github-actions-qt-creator@cristianadam.eu>
Reviewed-by: Alessandro Portale <alessandro.portale@qt.io>
I have noticed that some jobs fail due to missing ninja or ccache
executable.
With the 10 times retries I hope that these failures will go away.
Change-Id: I2d893e0c6cefc69bc4c5f841ae154d4f83f7a922
Reviewed-by: Eike Ziller <eike.ziller@qt.io>
Hopefully this will help with the macOS host which tends to fail
at running tests with:
The hosted runner: GitHub Actions X lost communication with the server.
Anything in your workflow that terminates the runner process, starves
it for CPU/Memory, or blocks its network access can cause this error.
Change-Id: I2ead1efd1526332cc2045fee7db4a76831f2e333
Reviewed-by: <github-actions-qt-creator@cristianadam.eu>
Reviewed-by: Eike Ziller <eike.ziller@qt.io>
By default it's 30 per page and one page. Increasing to 100 per page
and trying out 10 pages should provide recent results.
Change-Id: I46d8e20a35f94d2ef81cc0bbead4bade66a17f5a
Reviewed-by: Eike Ziller <eike.ziller@qt.io>
GitHub Actions cache action uses the branch name to scope the file
caching, which when using with a gerrit bot can lead to cache
misses.
By using the cache storage as an artifact we can always get the
artifacts if previous jobs created them.
By upgrading to v2 of actions/download/upload artifact we remove
the v1 problem of the upload action that creates a directory name
with the name of the artifact, which leads to failed release
uploads.
Change-Id: I8cb8c3242b58f709f51202852ad45d42b833fa84
Reviewed-by: Eike Ziller <eike.ziller@qt.io>
Also remove the pull_request support for github actions, since we
don't support the pull request workflow for contributions.
Change-Id: Ia0a1ab7c996f679195fde455c1f06911077d6deb
Reviewed-by: Eike Ziller <eike.ziller@qt.io>
The variable was not quoted and in certain cases the CMake code checking
for ccache clearing messages would error and the job would fail.
See 28a20b75bab8908e43ebf553a2ae2ef52775861b
Change-Id: I7703a547129b3294b6d8094035a272e5d35c5c60
Reviewed-by: Alessandro Portale <alessandro.portale@qt.io>
Update to latest v1 actions/cache, instead of using a fixed version.
For example v1.1.1 increased the cache version from 2GB to 5GB!
Change-Id: Ib312016f5e0e07771451049cf2d4cd3ce0225837
Reviewed-by: Alessandro Portale <alessandro.portale@qt.io>
This way master, which now is version 7 won't interfere with 6.0 branch
which will have version 6.
When branches share the same cache the ccache hit rate is now ~40%,
which is too low.
Reduce the ccache size so that the 5GB would host multiple branch
versions.
Change-Id: If29c917fb47f4e1fdab4b4257af8b0625f6f219e
Reviewed-by: <github-actions-qt-creator@cristianadam.eu>
Reviewed-by: Cristian Adam <cristian.adam@qt.io>