safe.bareRepository: default to "explicit" with WITH_BREAKING_CHANGES #2138
main.yml
on: push
config
7s
fuzz smoke test
1m 28s
static-analysis
5m 34s
rust-analysis
1m 47s
sparse
3m 30s
documentation
7m 11s
Matrix: dockerized
Matrix: regular
Matrix: win+VS test
Matrix: win+Meson test
Matrix: win test
Annotations
154 errors and 74 warnings
|
debian-11 (debian:11)
Process completed with exit code 2.
|
|
debian-11 (debian:11)
failed: t5540.15 non-fast-forward push show ref status
|
|
debian-11 (debian:11)
failed: t5540.14 non-fast-forward push fails
|
|
debian-11 (debian:11)
failed: t5540.13 PUT and MOVE sends object to URLs with SHA-1 hash suffix
|
|
debian-11 (debian:11)
failed: t5540.11 non-force push fails if not up to date
|
|
debian-11 (debian:11)
failed: t5540.10 create and delete remote branch
|
|
debian-11 (debian:11)
failed: t5540.9 http-push fetches packed objects
|
|
debian-11 (debian:11)
failed: t5540.8 http-push fetches unpacked objects
|
|
debian-11 (debian:11)
failed: t5540.7 push to remote repository with unpacked refs
|
|
debian-11 (debian:11)
failed: t5540.6 push already up-to-date
|
|
debian-11 (debian:11)
failed: t5540.5 push to remote repository with packed refs
|
|
linux-musl-meson (alpine:latest)
Process completed with exit code 1.
|
|
linux-musl-meson (alpine:latest)
Process completed with exit code 1.
|
|
linux-musl-meson (alpine:latest)
failed: t5541.12 non-fast-forward push show ref status
|
|
linux-musl-meson (alpine:latest)
failed: t5541.11 non-fast-forward push fails
|
|
linux-musl-meson (alpine:latest)
failed: t5541.10 rejected update prints status
|
|
linux-musl-meson (alpine:latest)
failed: t5541.8 create and delete remote branch
|
|
linux-musl-meson (alpine:latest)
failed: t5541.7 push already up-to-date
|
|
linux-musl-meson (alpine:latest)
failed: t5541.6 push to remote repository (standard) with sending Accept-Language
|
|
linux-musl-meson (alpine:latest)
failed: t5541.5 used receive-pack service
|
|
linux-musl-meson (alpine:latest)
failed: t5541.4 push to remote repository (standard)
|
|
linux-musl-meson (alpine:latest)
failed: t5541.3 clone remote repository
|
|
linux-breaking-changes (ubuntu:rolling)
failed: t5540.13 PUT and MOVE sends object to URLs with SHA-1 hash suffix
|
|
linux-breaking-changes (ubuntu:rolling)
failed: t5540.11 non-force push fails if not up to date
|
|
linux-breaking-changes (ubuntu:rolling)
failed: t5540.10 create and delete remote branch
|
|
linux-breaking-changes (ubuntu:rolling)
failed: t5540.9 http-push fetches packed objects
|
|
linux-breaking-changes (ubuntu:rolling)
failed: t5540.8 http-push fetches unpacked objects
|
|
linux-breaking-changes (ubuntu:rolling)
failed: t5540.7 push to remote repository with unpacked refs
|
|
linux-breaking-changes (ubuntu:rolling)
failed: t5540.6 push already up-to-date
|
|
linux-breaking-changes (ubuntu:rolling)
failed: t5540.5 push to remote repository with packed refs
|
|
linux-breaking-changes (ubuntu:rolling)
failed: t5003.82 archive remote http repository
|
|
linux-breaking-changes (ubuntu:rolling)
failed: t5003.79 setup for HTTP protocol
|
|
linux32 (i386/ubuntu:focal)
Process completed with exit code 2.
|
|
linux32 (i386/ubuntu:focal)
failed: t5540.15 non-fast-forward push show ref status
|
|
linux32 (i386/ubuntu:focal)
failed: t5540.14 non-fast-forward push fails
|
|
linux32 (i386/ubuntu:focal)
failed: t5540.13 PUT and MOVE sends object to URLs with SHA-1 hash suffix
|
|
linux32 (i386/ubuntu:focal)
failed: t5540.11 non-force push fails if not up to date
|
|
linux32 (i386/ubuntu:focal)
failed: t5540.10 create and delete remote branch
|
|
linux32 (i386/ubuntu:focal)
failed: t5540.9 http-push fetches packed objects
|
|
linux32 (i386/ubuntu:focal)
failed: t5540.8 http-push fetches unpacked objects
|
|
linux32 (i386/ubuntu:focal)
failed: t5540.7 push to remote repository with unpacked refs
|
|
linux32 (i386/ubuntu:focal)
failed: t5540.6 push already up-to-date
|
|
linux32 (i386/ubuntu:focal)
failed: t5540.5 push to remote repository with packed refs
|
|
linux-meson (ubuntu:rolling)
failed: t5540.15 non-fast-forward push show ref status
|
|
linux-meson (ubuntu:rolling)
failed: t5540.14 non-fast-forward push fails
|
|
linux-meson (ubuntu:rolling)
failed: t5540.13 PUT and MOVE sends object to URLs with SHA-1 hash suffix
|
|
linux-meson (ubuntu:rolling)
failed: t5540.11 non-force push fails if not up to date
|
|
linux-meson (ubuntu:rolling)
failed: t5540.10 create and delete remote branch
|
|
linux-meson (ubuntu:rolling)
failed: t5540.9 http-push fetches packed objects
|
|
linux-meson (ubuntu:rolling)
failed: t5540.8 http-push fetches unpacked objects
|
|
linux-meson (ubuntu:rolling)
failed: t5540.7 push to remote repository with unpacked refs
|
|
linux-meson (ubuntu:rolling)
failed: t5540.6 push already up-to-date
|
|
linux-meson (ubuntu:rolling)
failed: t5540.5 push to remote repository with packed refs
|
|
linux-TEST-vars (ubuntu:20.04)
Process completed with exit code 2.
|
|
linux-TEST-vars (ubuntu:20.04)
failed: t5540.15 non-fast-forward push show ref status
|
|
linux-TEST-vars (ubuntu:20.04)
failed: t5540.14 non-fast-forward push fails
|
|
linux-TEST-vars (ubuntu:20.04)
failed: t5540.13 PUT and MOVE sends object to URLs with SHA-1 hash suffix
|
|
linux-TEST-vars (ubuntu:20.04)
failed: t5540.11 non-force push fails if not up to date
|
|
linux-TEST-vars (ubuntu:20.04)
failed: t5540.10 create and delete remote branch
|
|
linux-TEST-vars (ubuntu:20.04)
failed: t5540.9 http-push fetches packed objects
|
|
linux-TEST-vars (ubuntu:20.04)
failed: t5540.8 http-push fetches unpacked objects
|
|
linux-TEST-vars (ubuntu:20.04)
failed: t5540.7 push to remote repository with unpacked refs
|
|
linux-TEST-vars (ubuntu:20.04)
failed: t5540.6 push already up-to-date
|
|
linux-TEST-vars (ubuntu:20.04)
failed: t5540.5 push to remote repository with packed refs
|
|
linux-sha256 (ubuntu:rolling)
failed: t5540.15 non-fast-forward push show ref status
|
|
linux-sha256 (ubuntu:rolling)
failed: t5540.14 non-fast-forward push fails
|
|
linux-sha256 (ubuntu:rolling)
failed: t5540.13 PUT and MOVE sends object to URLs with SHA-1 hash suffix
|
|
linux-sha256 (ubuntu:rolling)
failed: t5540.11 non-force push fails if not up to date
|
|
linux-sha256 (ubuntu:rolling)
failed: t5540.10 create and delete remote branch
|
|
linux-sha256 (ubuntu:rolling)
failed: t5540.9 http-push fetches packed objects
|
|
linux-sha256 (ubuntu:rolling)
failed: t5540.8 http-push fetches unpacked objects
|
|
linux-sha256 (ubuntu:rolling)
failed: t5540.7 push to remote repository with unpacked refs
|
|
linux-sha256 (ubuntu:rolling)
failed: t5540.6 push already up-to-date
|
|
linux-sha256 (ubuntu:rolling)
failed: t5540.5 push to remote repository with packed refs
|
|
linux-reftable (ubuntu:rolling)
Process completed with exit code 1.
|
|
linux-reftable (ubuntu:rolling)
failed: t5541.12 non-fast-forward push show ref status
|
|
linux-reftable (ubuntu:rolling)
failed: t5541.11 non-fast-forward push fails
|
|
linux-reftable (ubuntu:rolling)
failed: t5541.10 rejected update prints status
|
|
linux-reftable (ubuntu:rolling)
failed: t5541.8 create and delete remote branch
|
|
linux-reftable (ubuntu:rolling)
failed: t5541.7 push already up-to-date
|
|
linux-reftable (ubuntu:rolling)
failed: t5541.6 push to remote repository (standard) with sending Accept-Language
|
|
linux-reftable (ubuntu:rolling)
failed: t5541.5 used receive-pack service
|
|
linux-reftable (ubuntu:rolling)
failed: t5541.4 push to remote repository (standard)
|
|
linux-reftable (ubuntu:rolling)
failed: t5541.3 clone remote repository
|
|
osx-reftable (macos-14)
Process completed with exit code 1.
|
|
osx-reftable (macos-14)
failed: t5541.12 non-fast-forward push show ref status
|
|
osx-reftable (macos-14)
failed: t5541.11 non-fast-forward push fails
|
|
osx-reftable (macos-14)
failed: t5541.10 rejected update prints status
|
|
osx-reftable (macos-14)
failed: t5541.8 create and delete remote branch
|
|
osx-reftable (macos-14)
failed: t5541.7 push already up-to-date
|
|
osx-reftable (macos-14)
failed: t5541.6 push to remote repository (standard) with sending Accept-Language
|
|
osx-reftable (macos-14)
failed: t5541.5 used receive-pack service
|
|
osx-reftable (macos-14)
failed: t5541.4 push to remote repository (standard)
|
|
osx-reftable (macos-14)
failed: t5541.3 clone remote repository
|
|
osx-clang (macos-14)
failed: t5540.15 non-fast-forward push show ref status
|
|
osx-clang (macos-14)
failed: t5540.14 non-fast-forward push fails
|
|
osx-clang (macos-14)
failed: t5540.13 PUT and MOVE sends object to URLs with SHA-1 hash suffix
|
|
osx-clang (macos-14)
failed: t5540.11 non-force push fails if not up to date
|
|
osx-clang (macos-14)
failed: t5540.10 create and delete remote branch
|
|
osx-clang (macos-14)
failed: t5540.9 http-push fetches packed objects
|
|
osx-clang (macos-14)
failed: t5540.8 http-push fetches unpacked objects
|
|
osx-clang (macos-14)
failed: t5540.7 push to remote repository with unpacked refs
|
|
osx-clang (macos-14)
failed: t5540.6 push already up-to-date
|
|
osx-clang (macos-14)
failed: t5540.5 push to remote repository with packed refs
|
|
osx-gcc (macos-14)
failed: t5540.15 non-fast-forward push show ref status
|
|
osx-gcc (macos-14)
failed: t5540.14 non-fast-forward push fails
|
|
osx-gcc (macos-14)
failed: t5540.13 PUT and MOVE sends object to URLs with SHA-1 hash suffix
|
|
osx-gcc (macos-14)
failed: t5540.11 non-force push fails if not up to date
|
|
osx-gcc (macos-14)
failed: t5540.10 create and delete remote branch
|
|
osx-gcc (macos-14)
failed: t5540.9 http-push fetches packed objects
|
|
osx-gcc (macos-14)
failed: t5540.8 http-push fetches unpacked objects
|
|
osx-gcc (macos-14)
failed: t5540.7 push to remote repository with unpacked refs
|
|
osx-gcc (macos-14)
failed: t5540.6 push already up-to-date
|
|
osx-gcc (macos-14)
failed: t5540.5 push to remote repository with packed refs
|
|
osx-meson (macos-14)
failed: t5540.15 non-fast-forward push show ref status
|
|
osx-meson (macos-14)
failed: t5540.14 non-fast-forward push fails
|
|
osx-meson (macos-14)
failed: t5540.13 PUT and MOVE sends object to URLs with SHA-1 hash suffix
|
|
osx-meson (macos-14)
failed: t5540.11 non-force push fails if not up to date
|
|
osx-meson (macos-14)
failed: t5540.10 create and delete remote branch
|
|
osx-meson (macos-14)
failed: t5540.9 http-push fetches packed objects
|
|
osx-meson (macos-14)
failed: t5540.8 http-push fetches unpacked objects
|
|
osx-meson (macos-14)
failed: t5540.7 push to remote repository with unpacked refs
|
|
osx-meson (macos-14)
failed: t5540.6 push already up-to-date
|
|
osx-meson (macos-14)
failed: t5540.5 push to remote repository with packed refs
|
|
linux-reftable-leaks (ubuntu:rolling)
Process completed with exit code 1.
|
|
linux-reftable-leaks (ubuntu:rolling)
failed: t5541.12 non-fast-forward push show ref status
|
|
linux-reftable-leaks (ubuntu:rolling)
failed: t5541.11 non-fast-forward push fails
|
|
linux-reftable-leaks (ubuntu:rolling)
failed: t5541.10 rejected update prints status
|
|
linux-reftable-leaks (ubuntu:rolling)
failed: t5541.8 create and delete remote branch
|
|
linux-reftable-leaks (ubuntu:rolling)
failed: t5541.7 push already up-to-date
|
|
linux-reftable-leaks (ubuntu:rolling)
failed: t5541.6 push to remote repository (standard) with sending Accept-Language
|
|
linux-reftable-leaks (ubuntu:rolling)
failed: t5541.5 used receive-pack service
|
|
linux-reftable-leaks (ubuntu:rolling)
failed: t5541.4 push to remote repository (standard)
|
|
linux-reftable-leaks (ubuntu:rolling)
failed: t5541.3 clone remote repository
|
|
linux-leaks (ubuntu:rolling)
failed: t5540.15 non-fast-forward push show ref status
|
|
linux-leaks (ubuntu:rolling)
failed: t5540.14 non-fast-forward push fails
|
|
linux-leaks (ubuntu:rolling)
failed: t5540.13 PUT and MOVE sends object to URLs with SHA-1 hash suffix
|
|
linux-leaks (ubuntu:rolling)
failed: t5540.11 non-force push fails if not up to date
|
|
linux-leaks (ubuntu:rolling)
failed: t5540.10 create and delete remote branch
|
|
linux-leaks (ubuntu:rolling)
failed: t5540.9 http-push fetches packed objects
|
|
linux-leaks (ubuntu:rolling)
failed: t5540.8 http-push fetches unpacked objects
|
|
linux-leaks (ubuntu:rolling)
failed: t5540.7 push to remote repository with unpacked refs
|
|
linux-leaks (ubuntu:rolling)
failed: t5540.6 push already up-to-date
|
|
linux-leaks (ubuntu:rolling)
failed: t5540.5 push to remote repository with packed refs
|
|
linux-asan-ubsan (ubuntu:rolling)
failed: t5540.15 non-fast-forward push show ref status
|
|
linux-asan-ubsan (ubuntu:rolling)
failed: t5540.14 non-fast-forward push fails
|
|
linux-asan-ubsan (ubuntu:rolling)
failed: t5540.13 PUT and MOVE sends object to URLs with SHA-1 hash suffix
|
|
linux-asan-ubsan (ubuntu:rolling)
failed: t5540.11 non-force push fails if not up to date
|
|
linux-asan-ubsan (ubuntu:rolling)
failed: t5540.10 create and delete remote branch
|
|
linux-asan-ubsan (ubuntu:rolling)
failed: t5540.9 http-push fetches packed objects
|
|
linux-asan-ubsan (ubuntu:rolling)
failed: t5540.8 http-push fetches unpacked objects
|
|
linux-asan-ubsan (ubuntu:rolling)
failed: t5540.7 push to remote repository with unpacked refs
|
|
linux-asan-ubsan (ubuntu:rolling)
failed: t5540.6 push already up-to-date
|
|
linux-asan-ubsan (ubuntu:rolling)
failed: t5540.5 push to remote repository with packed refs
|
|
rust-analysis
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 will be forced to run with Node.js 24 by default starting June 2nd, 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/
|
|
win build
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/upload-artifact@v5, git-for-windows/setup-git-for-windows-sdk@v1. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
|
|
win+Meson build
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/upload-artifact@v5. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
|
|
win+Meson build
The `python-version` input is not set. The version of Python currently in `PATH` will be used.
|
|
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
|
|
debian-11 (debian:11)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/upload-artifact@v5. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
|
|
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
|
|
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
|
|
linux-musl-meson (alpine:latest)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/upload-artifact@v5. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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-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
|
|
linux-breaking-changes (ubuntu:rolling)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/upload-artifact@v5. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
|
|
linux32 (i386/ubuntu:focal)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/upload-artifact@v5. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
|
|
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
|
|
linux-meson (ubuntu:rolling)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/upload-artifact@v5. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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-TEST-vars (ubuntu:20.04)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/upload-artifact@v5. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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-sha256 (ubuntu:rolling)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/upload-artifact@v5. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
|
|
win test (0)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/download-artifact@v6, git-for-windows/setup-git-for-windows-sdk@v1. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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-reftable (ubuntu:rolling)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/upload-artifact@v5. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
|
|
win test (8)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/download-artifact@v6, git-for-windows/setup-git-for-windows-sdk@v1. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
|
|
win test (6)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/download-artifact@v6, git-for-windows/setup-git-for-windows-sdk@v1. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
|
|
win test (7)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/download-artifact@v6, git-for-windows/setup-git-for-windows-sdk@v1. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
|
|
win test (4)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/download-artifact@v6, git-for-windows/setup-git-for-windows-sdk@v1. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
|
|
win test (5)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/download-artifact@v6, git-for-windows/setup-git-for-windows-sdk@v1. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
|
|
win+Meson test (4)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/download-artifact@v6. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
|
|
win+Meson test (4)
The `python-version` input is not set. The version of Python currently in `PATH` will be used.
|
|
win+Meson test (9)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/download-artifact@v6. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
|
|
win+Meson test (9)
The `python-version` input is not set. The version of Python currently in `PATH` will be used.
|
|
osx-reftable (macos-14)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/upload-artifact@v5. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
|
|
osx-reftable (macos-14)
JGit wasn't installed, see above for clues why
|
|
osx-reftable (macos-14)
Already linked: /opt/homebrew/Cellar/gettext/1.0
|
|
win+Meson test (0)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/download-artifact@v6. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
|
|
win+Meson test (0)
The `python-version` input is not set. The version of Python currently in `PATH` will be used.
|
|
osx-clang (macos-14)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/upload-artifact@v5. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
|
|
osx-clang (macos-14)
JGit wasn't installed, see above for clues why
|
|
osx-clang (macos-14)
Already linked: /opt/homebrew/Cellar/gettext/1.0
|
|
win test (1)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/download-artifact@v6, git-for-windows/setup-git-for-windows-sdk@v1. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
|
|
win test (2)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/download-artifact@v6, git-for-windows/setup-git-for-windows-sdk@v1. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
|
|
osx-gcc (macos-14)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/upload-artifact@v5. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
|
|
osx-gcc (macos-14)
JGit wasn't installed, see above for clues why
|
|
osx-gcc (macos-14)
Already linked: /opt/homebrew/Cellar/gettext/1.0
|
|
win test (3)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/download-artifact@v6, git-for-windows/setup-git-for-windows-sdk@v1. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
|
|
osx-meson (macos-14)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/upload-artifact@v5. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
|
|
osx-meson (macos-14)
JGit wasn't installed, see above for clues why
|
|
osx-meson (macos-14)
pcre2 10.47_1 is already installed and up-to-date.
To reinstall 10.47_1, run:
brew reinstall pcre2
|
|
osx-meson (macos-14)
ninja 1.13.2 is already installed and up-to-date.
To reinstall 1.13.2, run:
brew reinstall ninja
|
|
osx-meson (macos-14)
Already linked: /opt/homebrew/Cellar/gettext/1.0
|
|
win+Meson test (3)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/download-artifact@v6. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
|
|
win+Meson test (3)
The `python-version` input is not set. The version of Python currently in `PATH` will be used.
|
|
win+Meson test (2)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/download-artifact@v6. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
|
|
win+Meson test (2)
The `python-version` input is not set. The version of Python currently in `PATH` will be used.
|
|
win test (9)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/download-artifact@v6, git-for-windows/setup-git-for-windows-sdk@v1. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
|
|
win+Meson test (1)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/download-artifact@v6. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
|
|
win+Meson test (1)
The `python-version` input is not set. The version of Python currently in `PATH` will be used.
|
|
win+Meson test (8)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/download-artifact@v6. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
|
|
win+Meson test (8)
The `python-version` input is not set. The version of Python currently in `PATH` will be used.
|
|
win+Meson test (5)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/download-artifact@v6. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
|
|
win+Meson test (5)
The `python-version` input is not set. The version of Python currently in `PATH` will be used.
|
|
win+Meson test (7)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/download-artifact@v6. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
|
|
win+Meson test (7)
The `python-version` input is not set. The version of Python currently in `PATH` will be used.
|
|
linux-reftable-leaks (ubuntu:rolling)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/upload-artifact@v5. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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-leaks (ubuntu:rolling)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/upload-artifact@v5. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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-asan-ubsan (ubuntu:rolling)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/upload-artifact@v5. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
|
|
win+Meson test (6)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/download-artifact@v6. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
|
|
win+Meson test (6)
The `python-version` input is not set. The version of Python currently in `PATH` will be used.
|
Artifacts
Produced during runtime
| Name | Size | Digest | |
|---|---|---|---|
|
failed-tests-debian-11
|
164 KB |
sha256:e538af7c7d7f62fe8f94eda55042901aa182135e7e9f0f2ab18b5e9356db732e
|
|
|
failed-tests-linux-TEST-vars
|
167 KB |
sha256:f48404a9d4b609744b17ce648127b4c26d7da5bbd8d76d06cd890544abb6ecba
|
|
|
failed-tests-linux-asan-ubsan
|
158 KB |
sha256:c77b04df99ee075118264cc1276164a0b165172d82dca4fa58c284e53270f453
|
|
|
failed-tests-linux-breaking-changes
|
1.97 MB |
sha256:1a078e3021a1780c3b4fa989ed59cf87216a00c1cb730d3255f8a90eb259ea12
|
|
|
failed-tests-linux-leaks
|
161 KB |
sha256:443728a7e60dd13d9f2bfeeb7c468348431851a50d9b0a743f855544dcba49c9
|
|
|
failed-tests-linux-meson
|
165 KB |
sha256:7cc71b1fd00a10c58695961e6a3f63d3fc6df758b1dcf270943414b0a41b2c0f
|
|
|
failed-tests-linux-musl-meson
|
44.3 KB |
sha256:176af43da747082cf8268b1d996667861880e470131bb07817ccbdbf7cfcc430
|
|
|
failed-tests-linux-reftable
|
41.7 KB |
sha256:7036b3c91715b10d47fda4264cb9da7beff643a2dd918b295cb8d8015c49bee1
|
|
|
failed-tests-linux-reftable-leaks
|
44.4 KB |
sha256:5093af46310bef3a778799c447a22b78d1bb8a2523f7f34415c8b51963110004
|
|
|
failed-tests-linux-sha256
|
167 KB |
sha256:93de918421f26f98ec7b61fc3c3b227933143292ed7ee5294160a29d98c64b72
|
|
|
failed-tests-linux32
|
162 KB |
sha256:6be5677e97cc4b5332fc452215c8eecd9bbefec590fe4c2ccd01ee2a67416929
|
|
|
failed-tests-osx-clang
|
168 KB |
sha256:098ffee422fe4275ec5e9a97c336a3c13e00a831757d643b9ba1570aba6eb276
|
|
|
failed-tests-osx-gcc
|
168 KB |
sha256:bcf6ded065ecd11b06ee5d841f2ad81c943b96cba717a0cb021ac88fdc76f94e
|
|
|
failed-tests-osx-meson
|
168 KB |
sha256:b248077ae74352be2bceb9ef81f5b231f930f88c9e4869b09cba7414254baed8
|
|
|
failed-tests-osx-reftable
|
47.2 KB |
sha256:1982116f6abed988569c0570022550fb7c2be3f5ec2475f90ed262e608751eb5
|
|
|
windows-artifacts
|
96.8 MB |
sha256:1580e10ad9bfd42537e67f1d847f81d22af0777468be6a4a5c446eba3385c7a4
|
|
|
windows-meson-artifacts
|
48.1 MB |
sha256:8a670e84adc0d8085d69a6dc47609828837c60082c108ca8c5d88d0ffc7581e0
|
|