fixup??? survey: summarize total sizes by object type #5985
dschomain.yml
on: push
config
7s
Matrix: win+VS build
fuzz smoke test
1m 31s
static-analysis
5m 55s
sparse
3m 43s
documentation
9m 18s
Matrix: dockerized
Matrix: regular
Matrix: win+VS test
Matrix: win+Meson test
Matrix: win test
Annotations
7 errors, 30 warnings, and 14 notices
|
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
|
|
win+Meson build
Process completed with exit code 1.
|
|
fedora-breaking-changes-meson (fedora:latest)
Process completed with exit code 1.
|
|
win test (6)
Process completed with exit code 1.
|
|
win test (6)
failed: t7429.2 recursive submodule with a long path
|
|
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>06G7WaAAAAAAEU6uuHXW1QrZ9X1y1ugffUEhMMzBFREdFMDIyMQBFZGdl
|
|
win+VS build (arm64)
Failed to restore: Cache service responded with 400
|
|
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>06m7WaAAAAADcvB3jj4TjRL9iecZFbL/BQlkzRURHRTAxMjEARWRnZQ==
|
|
win+VS build (x64)
Failed to restore: Cache service responded with 400
|
|
win+Meson build
The `python-version` input is not set. The version of Python currently in `PATH` will be used.
|
|
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
|
|
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
|
|
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
|
|
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
|
|
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-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-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.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
|
|
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+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 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 (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 (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 (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 (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 (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 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 (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 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 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 (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 | |
|---|---|---|---|
|
failed-tests-windows-6
Expired
|
127 KB |
sha256:578599cbf232ecfe65aa71ed930f2c5a82839758bdd1ca95f2c67c5913cb71b9
|
|
|
windows-artifacts
Expired
|
99.1 MB |
sha256:49e37a003a86a778a57ff56128ecae7c6e16abd2b6b8ccb07b445869f43bc223
|
|