comment logging #2005
ci.yml
on: push
coverage - measure
4m 46s
lint
4m 47s
macosx
3m 43s
android
8m 12s
Matrix: conan - emscripten
Matrix: conan-linux
Matrix: conan-macosx
Matrix: deb
Matrix: msys2
Matrix: sanitizer
Matrix: vcpkg-ios
Matrix: vcpkg-linux
Matrix: vcpkg-windows
Annotations
9 errors and 16 warnings
|
sanitizer - debian:trixie
Process completed with exit code 2.
|
|
conan - macos-latest
Process completed with exit code 1.
|
|
sanitizer - arm64v8/debian:trixie
Process completed with exit code 2.
|
|
macosx
Process completed with exit code 2.
|
|
conan - emscripten (debian, bookworm)
Process completed with exit code 1.
|
|
sanitizer - arm32v7/debian:trixie
Process completed with exit code 2.
|
|
lint
Process completed with exit code 2.
|
|
msys2 - mingw64
Process completed with exit code 4.
|
|
msys2 - mingw32
Process completed with exit code 4.
|
|
macosx
cppfw/tap/libr4 1.0.109 already installed
|
|
macosx
freetype 2.14.2 already installed
|
|
macosx
cppfw/tap/libutki 1.1.292 already installed
|
|
macosx
cppfw/tap/myci 0.1.224 already installed
|
|
coverage - measure
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/github-script@60a0d83039c74a4aee543508d2ffcb1c3799cdea, actions/upload-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
|
|
vcpkg - ios | Debug
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/upload-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
|
|
vcpkg - ios | Debug
cmake 4.2.3 is already installed and up-to-date.
To reinstall 4.2.3, run:
brew reinstall cmake
|
|
vcpkg - ios | Release
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/upload-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
|
|
vcpkg - ios | Release
cmake 4.2.3 is already installed and up-to-date.
To reinstall 4.2.3, run:
brew reinstall cmake
|
|
msys2 - mingw64
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: msys2/setup-msys2@v2. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
|
|
vcpkg - linux |
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/upload-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
|
|
msys2 - mingw32
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: msys2/setup-msys2@v2. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
|
|
vcpkg - windows - x64 | Debug
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/upload-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
|
|
vcpkg - windows - x64 | Release
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/upload-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
|
|
vcpkg - windows - Win32 | Release
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/upload-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
|
|
vcpkg - windows - Win32 | Debug
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/upload-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
|
Artifacts
Produced during runtime
| Name | Size | Digest | |
|---|---|---|---|
|
cobertura.xml
|
64.9 KB |
sha256:6028f02d289c03da40a1ba70c7d48f20b267dbedc012eea3fe274979414c2b12
|
|
|
vcpkg_ios_Debug_logs
|
70.5 MB |
sha256:c134491c72e7a63a17e6e7920d6b96fd4bc3a76a4a120a8c9dc886ace550a9f3
|
|
|
vcpkg_ios_Release_logs
|
70.5 MB |
sha256:805dcbece2a1af2333f90a483d59bb0d607099a19c102e38490983a530cb7393
|
|
|
vcpkg_linux_logs
|
73.5 MB |
sha256:fe4e557dfce69630e77dc5ae4ce040a9503193462bd1894e65625db5f0a319d2
|
|
|
vcpkg_windows_Win32_Debug_logs
|
149 MB |
sha256:f1ae2c599fa34b22ed9ee2e71940055b8a91c6081be844b433fa9ec38da962b6
|
|
|
vcpkg_windows_Win32_Release_logs
|
149 MB |
sha256:067e3344d78b1d456b2b8771a45152bd1592f39d8f534395260eb856ff88acc6
|
|
|
vcpkg_windows_x64_Debug_logs
|
158 MB |
sha256:8e5191ae67bd9c2797e23f8a06a5f075d6cd44d3dbe6e047e4bfd08ec63a0bf9
|
|
|
vcpkg_windows_x64_Release_logs
|
158 MB |
sha256:e45cfd0f7d3165c0959f8c6b7713cea5ca8ad8733b3e31e086d3635af6f4180d
|
|