QT6, let's see how it goes #13670
main.yml
on: pull_request
android-build
9m 16s
Matrix: window-build
Matrix: window-msvc2022-build
linux-x86-build
1m 55s
ios-build
5m 28s
raspberry-pi-build
14s
window-msvc2022-aiserver-build
17m 25s
raspberry-pi-build-and-image-64bit
1m 27s
Matrix: android-emulator-test
upload_to_release
0s
Annotations
10 errors, 38 warnings, and 5 notices
|
raspberry-pi-build
Docker pull failed with exit code 1
|
|
linux-x86-build
Process completed with exit code 2.
|
|
raspberry-pi-build-and-image-64bit
Process completed with exit code 2.
|
|
window-build (true)
Error: The process 'C:\hostedtoolcache\windows\Python\3.11.9\x64\python.exe' failed with exit code 1
|
|
window-build (false)
The strategy configuration was canceled because "window-build.true" failed
|
|
window-build (false)
Error: The process 'C:\hostedtoolcache\windows\Python\3.11.9\x64\python.exe' failed with exit code 1
|
|
ios-build
Process completed with exit code 127.
|
|
ios-build
Process completed with exit code 1.
|
|
android-build
Process completed with exit code 2.
|
|
window-msvc2022-aiserver-build
Process completed with exit code 1.
|
|
raspberry-pi-build
Docker pull failed with exit code 1, back off 5.155 seconds before retry.
|
|
raspberry-pi-build
Docker pull failed with exit code 1, back off 4.224 seconds before retry.
|
|
linux-x86-build
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, actions/checkout@v4, actions/setup-python@v5, actions/upload-artifact@v4, jurplel/install-qt-action/action@v3. Actions will be forced to run with Node.js 24 by default starting June 16th, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
linux-x86-build
No files were found with the provided path: tst/test-artifacts/*.fit
tst/test-artifacts/*.sqlite. No artifacts will be uploaded.
|
|
linux-x86-build
No files were found with the provided path: tst/test-results/**/*.xml. No artifacts will be uploaded.
|
|
linux-x86-build
Failed to save: <h2>Our services aren't available right now</h2><p>We're working to restore all services as soon as possible. Please check back soon.</p>06/AnagAAAABAnHD8ABONQqk8JMZLh/kyTEFYRURHRTE2MTUARWRnZQ==
|
|
linux-x86-build
Failed to restore: Cache service responded with 400
|
|
raspberry-pi-build-and-image-64bit
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v2. Actions will be forced to run with Node.js 24 by default starting June 16th, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
window-build (true)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v2, actions/setup-python@v4, actions/setup-python@v5, jurplel/install-qt-action/action@v3, jwlawson/actions-setup-cmake@v1.9. Actions will be forced to run with Node.js 24 by default starting June 16th, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
window-build (true)
Failed to restore: Cache service responded with 400
|
|
window-build (false)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v2, actions/setup-python@v4, actions/setup-python@v5, jurplel/install-qt-action/action@v3, jwlawson/actions-setup-cmake@v1.9. Actions will be forced to run with Node.js 24 by default starting June 16th, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
window-build (false)
Failed to restore: Cache service responded with 400
|
|
ios-build
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/setup-python@v5, jurplel/install-qt-action/action@v3. Actions will be forced to run with Node.js 24 by default starting June 16th, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
ios-build
Failed to save: <h2>Our services aren't available right now</h2><p>We're working to restore all services as soon as possible. Please check back soon.</p>0xvEnagAAAAAbxAO0nc7FRJjjK8oXS8b8U04xRURHRTIyMDcARWRnZQ==
|
|
ios-build
p7zip 17.06 is already installed and up-to-date.
To reinstall 17.06, run:
brew reinstall p7zip
|
|
ios-build
Failed to restore: Cache service responded with 400
|
|
android-build
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, actions/checkout@v3, actions/setup-java@v3, actions/setup-python@v5, gradle/gradle-build-action@v2, jurplel/install-qt-action/action@v3. Actions will be forced to run with Node.js 24 by default starting June 16th, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
android-build
Restore Gradle distribution 8.7 failed: Error: Cache service responded with 400
|
|
android-build
Failed to restore v8-gradle|Linux|ci-android-build[37a6259cc0c1dae299a7866489dff0bd]-3e72d924e18935e7a004db8506c8f2be087d5687: Error: Cache service responded with 400
|
|
android-build
Failed to save: <h2>Our services aren't available right now</h2><p>We're working to restore all services as soon as possible. Please check back soon.</p>0qPInagAAAAAplECzhpLyTIXp0oFY5xKuUEhMMzBFREdFMDEwOQBFZGdl
|
|
android-build
Failed to restore: Cache service responded with 400
|
|
android-build
Failed to save: <h2>Our services aren't available right now</h2><p>We're working to restore all services as soon as possible. Please check back soon.</p>0P/InagAAAACFSj9sBq+3Q4f587zsyJSsUEhMMzBFREdFMDEwOQBFZGdl
|
|
android-build
Failed to restore: Cache service responded with 400
|
|
android-build
Failed to save: <h2>Our services aren't available right now</h2><p>We're working to restore all services as soon as possible. Please check back soon.</p>03/EnagAAAAAW6/NzZoLiS7/jmir9wCF5UEhMMzBFREdFMDEwOQBFZGdl
|
|
android-build
Failed to restore: Cache service responded with 400
|
|
android-build
Failed to save: <h2>Our services aren't available right now</h2><p>We're working to restore all services as soon as possible. Please check back soon.</p>0ifEnagAAAACJlioW4jPnQraLxYdIdkonUEhMMzBFREdFMDEwOQBFZGdl
|
|
android-build
Failed to restore: Cache service responded with 400
|
|
android-build
Failed to save: <h2>Our services aren't available right now</h2><p>We're working to restore all services as soon as possible. Please check back soon.</p>0RPEnagAAAAB/NqHckQs2Tq8eRGuPK3DtUEhMMzBFREdFMDEwOQBFZGdl
|
|
android-build
Failed to restore: Cache service responded with 400
|
|
window-msvc2022-aiserver-build
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v2, actions/setup-python@v5, ilammy/msvc-dev-cmd@v1, jurplel/install-qt-action/action@v3. Actions will be forced to run with Node.js 24 by default starting June 16th, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
window-msvc2022-aiserver-build
Failed to save: <h2>Our services aren't available right now</h2><p>We're working to restore all services as soon as possible. Please check back soon.</p>0L/EnagAAAAC6WgH5C8yxQL+QH4u+Is3PUEhMMzBFREdFMDExMwBFZGdl
|
|
window-msvc2022-aiserver-build
Failed to restore: Cache service responded with 400
|
|
window-msvc2022-build (true)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v2, actions/setup-python@v4, actions/setup-python@v5, actions/upload-artifact@v4, ilammy/msvc-dev-cmd@v1, jurplel/install-qt-action/action@v3. Actions will be forced to run with Node.js 24 by default starting June 16th, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
window-msvc2022-build (true)
Failed to save: <h2>Our services aren't available right now</h2><p>We're working to restore all services as soon as possible. Please check back soon.</p>0nvEnagAAAABfIAA5zgEsSaAAV9pLh99mTEFYMzExMDAwMTEyMDM1AEVkZ2U=
|
|
window-msvc2022-build (true)
Failed to restore: Cache service responded with 400
|
|
window-msvc2022-build (false)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v2, actions/setup-python@v4, actions/setup-python@v5, actions/upload-artifact@v4, ilammy/msvc-dev-cmd@v1, jurplel/install-qt-action/action@v3. Actions will be forced to run with Node.js 24 by default starting June 16th, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
window-msvc2022-build (false)
Failed to save: <h2>Our services aren't available right now</h2><p>We're working to restore all services as soon as possible. Please check back soon.</p>0kvEnagAAAABlVzR0WoNARJS10es0DaUJQ0hJMzBFREdFMDMyMQBFZGdl
|
|
window-msvc2022-build (false)
Failed to restore: Cache service responded with 400
|
|
window-build (true)
NOTICE: windows-latest requests are being redirected to windows-2025-vs2026 by June 15, 2026
|
|
window-build (false)
NOTICE: windows-latest requests are being redirected to windows-2025-vs2026 by June 15, 2026
|
|
window-msvc2022-aiserver-build
NOTICE: windows-latest requests are being redirected to windows-2025-vs2026 by June 15, 2026
|
|
window-msvc2022-build (true)
NOTICE: windows-latest requests are being redirected to windows-2025-vs2026 by June 15, 2026
|
|
window-msvc2022-build (false)
NOTICE: windows-latest requests are being redirected to windows-2025-vs2026 by June 15, 2026
|
Artifacts
Produced during runtime
| Name | Size | Digest | |
|---|---|---|---|
|
windows-msvc2022-binary
|
498 MB |
sha256:01d2663daead77d142a988a066f76ac6da1b3fa5624fdc13ff03839f68448ff4
|
|
|
windows-msvc2022-binary-no-python
|
373 MB |
sha256:7614afa0ad68e424e5ecced0fe0579e5155d0a190174e3974598d456ee8244c8
|
|