Skip to content

Merge 'readme' into HEAD #5845

Merge 'readme' into HEAD

Merge 'readme' into HEAD #5845

Triggered via push August 7, 2025 11:52
Status Success
Total duration 42m 5s
Artifacts 4

main.yml

on: push
Matrix: win+VS build
win+Meson build
3m 23s
win+Meson build
Matrix: dockerized
Matrix: regular
Matrix: win+VS test
Matrix: win+Meson test
Matrix: win test
Fit to window
Zoom out
Zoom in

Annotations

40 warnings and 34 notices
pedantic (fedora:latest)
JGit wasn't installed, see above for clues why
pedantic (fedora:latest)
git-lfs wasn't installed, see above for clues why
pedantic (fedora:latest)
perforce wasn't installed, see above for clues why
win+Meson build
The `python-version` input is not set. The version of Python currently in `PATH` will be used.
win+VS build (x64)
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>0xZOUaAAAAAD7XPC0048FQ4wWRcNq5jhQRE0yRURHRTA3MTkARWRnZQ==
win+VS build (x64)
Failed to restore: Cache service responded with 400
win+VS build (arm64)
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>0xpOUaAAAAAAs0l5nNVoCQbDjo7laLcs0UEhYMzFFREdFMDUxMwBFZGdl
win+VS build (arm64)
Failed to restore: Cache service responded with 400
linux-musl-meson (alpine:latest)
JGit wasn't installed, see above for clues why
linux-musl-meson (alpine:latest)
git-lfs wasn't installed, see above for clues why
linux-musl-meson (alpine:latest)
perforce wasn't installed, see above for clues why
debian-11 (debian:11)
JGit wasn't installed, see above for clues why
debian-11 (debian:11)
git-lfs wasn't installed, see above for clues why
debian-11 (debian:11)
perforce wasn't installed, see above for clues why
linux32 (i386/ubuntu:focal)
JGit wasn't installed, see above for clues why
linux32 (i386/ubuntu:focal)
git-lfs wasn't installed, see above for clues why
linux32 (i386/ubuntu:focal)
perforce wasn't installed, see above for clues why
win+Meson test (7)
The `python-version` input is not set. The version of Python currently in `PATH` will be used.
win+Meson test (3)
The `python-version` input is not set. The version of Python currently in `PATH` will be used.
almalinux-8 (almalinux:8)
JGit wasn't installed, see above for clues why
almalinux-8 (almalinux:8)
git-lfs wasn't installed, see above for clues why
almalinux-8 (almalinux:8)
perforce wasn't installed, see above for clues why
win+Meson test (2)
The `python-version` input is not set. The version of Python currently in `PATH` will be used.
win+Meson test (5)
The `python-version` input is not set. The version of Python currently in `PATH` will be used.
win+Meson test (6)
The `python-version` input is not set. The version of Python currently in `PATH` will be used.
win+Meson test (8)
The `python-version` input is not set. The version of Python currently in `PATH` will be used.
win+Meson test (4)
The `python-version` input is not set. The version of Python currently in `PATH` will be used.
win+Meson test (0)
The `python-version` input is not set. The version of Python currently in `PATH` will be used.
win+Meson test (9)
The `python-version` input is not set. The version of Python currently in `PATH` will be used.
win+Meson test (1)
The `python-version` input is not set. The version of Python currently in `PATH` will be used.
osx-gcc (macos-13)
JGit wasn't installed, see above for clues why
osx-gcc (macos-13)
Already linked: /usr/local/Cellar/gettext/0.26
osx-meson (macos-13)
JGit wasn't installed, see above for clues why
osx-meson (macos-13)
pcre2 10.45 is already installed and up-to-date. To reinstall 10.45, run: brew reinstall pcre2
osx-meson (macos-13)
ninja 1.13.1 is already installed and up-to-date. To reinstall 1.13.1, run: brew reinstall ninja
osx-meson (macos-13)
Already linked: /usr/local/Cellar/gettext/0.26
osx-clang (macos-13)
JGit wasn't installed, see above for clues why
osx-clang (macos-13)
Already linked: /usr/local/Cellar/gettext/0.26
osx-reftable (macos-13)
JGit wasn't installed, see above for clues why
osx-reftable (macos-13)
Already linked: /usr/local/Cellar/gettext/0.26
win+Meson build
The windows-latest label will migrate from Windows Server 2022 to Windows Server 2025 beginning September 2, 2025. For more information see https://github.com/actions/runner-images/issues/12677
win+VS build (x64)
The windows-latest label will migrate from Windows Server 2022 to Windows Server 2025 beginning September 2, 2025. For more information see https://github.com/actions/runner-images/issues/12677
win+VS build (arm64)
The windows-latest label will migrate from Windows Server 2022 to Windows Server 2025 beginning September 2, 2025. For more information see https://github.com/actions/runner-images/issues/12677
win build
The windows-latest label will migrate from Windows Server 2022 to Windows Server 2025 beginning September 2, 2025. For more information see https://github.com/actions/runner-images/issues/12677
win+Meson test (7)
The windows-latest label will migrate from Windows Server 2022 to Windows Server 2025 beginning September 2, 2025. For more information see https://github.com/actions/runner-images/issues/12677
win+Meson test (3)
The windows-latest label will migrate from Windows Server 2022 to Windows Server 2025 beginning September 2, 2025. For more information see https://github.com/actions/runner-images/issues/12677
win+Meson test (2)
The windows-latest label will migrate from Windows Server 2022 to Windows Server 2025 beginning September 2, 2025. For more information see https://github.com/actions/runner-images/issues/12677
win+Meson test (5)
The windows-latest label will migrate from Windows Server 2022 to Windows Server 2025 beginning September 2, 2025. For more information see https://github.com/actions/runner-images/issues/12677
win+VS test (8)
The windows-latest label will migrate from Windows Server 2022 to Windows Server 2025 beginning September 2, 2025. For more information see https://github.com/actions/runner-images/issues/12677
win+Meson test (6)
The windows-latest label will migrate from Windows Server 2022 to Windows Server 2025 beginning September 2, 2025. For more information see https://github.com/actions/runner-images/issues/12677
win+Meson test (8)
The windows-latest label will migrate from Windows Server 2022 to Windows Server 2025 beginning September 2, 2025. For more information see https://github.com/actions/runner-images/issues/12677
win+Meson test (4)
The windows-latest label will migrate from Windows Server 2022 to Windows Server 2025 beginning September 2, 2025. For more information see https://github.com/actions/runner-images/issues/12677
win+Meson test (0)
The windows-latest label will migrate from Windows Server 2022 to Windows Server 2025 beginning September 2, 2025. For more information see https://github.com/actions/runner-images/issues/12677
win+VS test (7)
The windows-latest label will migrate from Windows Server 2022 to Windows Server 2025 beginning September 2, 2025. For more information see https://github.com/actions/runner-images/issues/12677
win+VS test (5)
The windows-latest label will migrate from Windows Server 2022 to Windows Server 2025 beginning September 2, 2025. For more information see https://github.com/actions/runner-images/issues/12677
win+VS test (1)
The windows-latest label will migrate from Windows Server 2022 to Windows Server 2025 beginning September 2, 2025. For more information see https://github.com/actions/runner-images/issues/12677
win+Meson test (9)
The windows-latest label will migrate from Windows Server 2022 to Windows Server 2025 beginning September 2, 2025. For more information see https://github.com/actions/runner-images/issues/12677
win+VS test (6)
The windows-latest label will migrate from Windows Server 2022 to Windows Server 2025 beginning September 2, 2025. For more information see https://github.com/actions/runner-images/issues/12677
win+VS test (3)
The windows-latest label will migrate from Windows Server 2022 to Windows Server 2025 beginning September 2, 2025. For more information see https://github.com/actions/runner-images/issues/12677
win+Meson test (1)
The windows-latest label will migrate from Windows Server 2022 to Windows Server 2025 beginning September 2, 2025. For more information see https://github.com/actions/runner-images/issues/12677
win test (1)
The windows-latest label will migrate from Windows Server 2022 to Windows Server 2025 beginning September 2, 2025. For more information see https://github.com/actions/runner-images/issues/12677
win+VS test (4)
The windows-latest label will migrate from Windows Server 2022 to Windows Server 2025 beginning September 2, 2025. For more information see https://github.com/actions/runner-images/issues/12677
win test (8)
The windows-latest label will migrate from Windows Server 2022 to Windows Server 2025 beginning September 2, 2025. For more information see https://github.com/actions/runner-images/issues/12677
win+VS test (2)
The windows-latest label will migrate from Windows Server 2022 to Windows Server 2025 beginning September 2, 2025. For more information see https://github.com/actions/runner-images/issues/12677
win test (3)
The windows-latest label will migrate from Windows Server 2022 to Windows Server 2025 beginning September 2, 2025. For more information see https://github.com/actions/runner-images/issues/12677
win+VS test (0)
The windows-latest label will migrate from Windows Server 2022 to Windows Server 2025 beginning September 2, 2025. For more information see https://github.com/actions/runner-images/issues/12677
win test (7)
The windows-latest label will migrate from Windows Server 2022 to Windows Server 2025 beginning September 2, 2025. For more information see https://github.com/actions/runner-images/issues/12677
win+VS test (9)
The windows-latest label will migrate from Windows Server 2022 to Windows Server 2025 beginning September 2, 2025. For more information see https://github.com/actions/runner-images/issues/12677
win test (6)
The windows-latest label will migrate from Windows Server 2022 to Windows Server 2025 beginning September 2, 2025. For more information see https://github.com/actions/runner-images/issues/12677
win test (4)
The windows-latest label will migrate from Windows Server 2022 to Windows Server 2025 beginning September 2, 2025. For more information see https://github.com/actions/runner-images/issues/12677
win test (9)
The windows-latest label will migrate from Windows Server 2022 to Windows Server 2025 beginning September 2, 2025. For more information see https://github.com/actions/runner-images/issues/12677
win test (2)
The windows-latest label will migrate from Windows Server 2022 to Windows Server 2025 beginning September 2, 2025. For more information see https://github.com/actions/runner-images/issues/12677
win test (5)
The windows-latest label will migrate from Windows Server 2022 to Windows Server 2025 beginning September 2, 2025. For more information see https://github.com/actions/runner-images/issues/12677
win test (0)
The windows-latest label will migrate from Windows Server 2022 to Windows Server 2025 beginning September 2, 2025. For more information see https://github.com/actions/runner-images/issues/12677

Artifacts

Produced during runtime
Name Size Digest
vs-artifacts-arm64
27.7 MB
sha256:1d87e2e7ec8fbe8940b8065fe8276a259c1ec180353c1e03ff4937a95a75fcb4
vs-artifacts-x64
28.7 MB
sha256:78020486319f732484d15735b3609f6a57f0fcefa86087c1470d3463124ec841
windows-artifacts
98.4 MB
sha256:b572b7ca87d93d9bc8f6ceb292e3267d46ab579aec626c1e9077b522844f0ff2
windows-meson-artifacts
35.4 MB
sha256:ea82693bb23fc74c530311ee3bac3c7e02f4f12b9ba3bd4e2754b22a6b36b148