Skip to content

Merge branch 'cs/subtree-squash-split-fix' #5998

Merge branch 'cs/subtree-squash-split-fix'

Merge branch 'cs/subtree-squash-split-fix' #5998

Triggered via push September 29, 2025 22:46
Status Failure
Total duration 1h 57m 17s
Artifacts 2

main.yml

on: push
Matrix: win+VS build
win+Meson build
3m 22s
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

7 errors, 29 warnings, and 5 notices
win+Meson build
Process completed with exit code 1.
win+VS build (arm64)
Process completed with exit code 1.
win+VS build (x64)
The operation was canceled.
win+VS build (x64)
The strategy configuration was canceled because "vs-build.arm64" failed
fedora-breaking-changes-meson (fedora:latest)
Process completed with exit code 1.
win test (7)
Process completed with exit code 1.
win test (7)
failed: t7429.2 recursive submodule with a long path
win+Meson build
The `python-version` input is not set. The version of Python currently in `PATH` will be used.
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>06BrbaAAAAABU6C6fB28uRolg9h2cjkL+UEhMMzBFREdFMDExMwBFZGdl
win+VS build (arm64)
Failed to restore: Cache service responded with 400
win+VS build (x64)
Failed to restore: Cache service responded with 400
fedora-breaking-changes-meson (fedora:latest)
JGit wasn't installed, see above for clues why
fedora-breaking-changes-meson (fedora:latest)
git-lfs wasn't installed, see above for clues why
fedora-breaking-changes-meson (fedora:latest)
perforce wasn't installed, see above for clues why
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
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
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
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
osx-meson (macos-13)
JGit wasn't installed, see above for clues why
osx-meson (macos-13)
pcre2 10.46 is already installed and up-to-date. To reinstall 10.46, 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-gcc (macos-13)
JGit wasn't installed, see above for clues why
osx-gcc (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 (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+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 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 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

Artifacts

Produced during runtime
Name Size Digest
failed-tests-windows-7 Expired
127 KB
sha256:43942c4024bd91aa20f0a3daf394fad0151a3d9229be233ce41edbe98a2852a7
windows-artifacts Expired
99.1 MB
sha256:f8c549aa20f1b3d71eb13c36c24681e1e40ce87f08237d3b5c30ab3b73d3ff25