Skip to content

fixup??? survey: stub in new experimental 'git-survey' command #6945

fixup??? survey: stub in new experimental 'git-survey' command

fixup??? survey: stub in new experimental 'git-survey' command #6945

Triggered via push August 12, 2026 07:10
Status Failure
Total duration 56m 1s
Artifacts 4

main.yml

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

Annotations

6 errors and 45 warnings
win build
Process completed with exit code 1.
win build: list-objects-filter.c#L858
list-objects-filter.c:858:28: assignment to 'size_t *' {aka 'long long unsigned int *'} from incompatible pointer type 'long unsigned int *' [-Wincompatible-pointer-types]
linux32 (i386/ubuntu:20.04)
Process completed with exit code 1.
linux32 (i386/ubuntu:20.04): list-objects-filter.c#L858
list-objects-filter.c:858:14: assignment to 'size_t *' {aka 'unsigned int *'} from incompatible pointer type 'long unsigned int *' [-Werror=incompatible-pointer-types]
linux-breaking-changes (ubuntu:rolling)
Process completed with exit code 1.
linux-breaking-changes (ubuntu:rolling)
failed: t3455.16 --no-edit uses last "amend!" message without an editor
linux32 (i386/ubuntu:20.04)
JGit wasn't installed, see above for clues why
linux32 (i386/ubuntu:20.04)
git-lfs wasn't installed, see above for clues why
linux32 (i386/ubuntu:20.04)
perforce wasn't installed, see above for clues why
win+VS build (x64)
Node.js 20 is deprecated. The following actions target Node.js 20 but are being forced to run on Node.js 24: git-for-windows/get-azure-pipelines-artifact@v0. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
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>03Bx8agAAAAACNWbmMllhSIpmGEnm0ZKfUEhMMzBFREdFMDExNwBFZGdl
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.
win+VS build (arm64)
Node.js 20 is deprecated. The following actions target Node.js 20 but are being forced to run on Node.js 24: git-for-windows/get-azure-pipelines-artifact@v0. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
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>03Bx8agAAAAA/rt/sHKEtQ4f1zj72aTMJUEhMMzBFREdFMDQwOABFZGdl
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
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
win+Meson test (3)
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
win+Meson test (4)
The `python-version` input is not set. The version of Python currently in `PATH` will be used.
win+Meson test (2)
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 (7)
The `python-version` input is not set. The version of Python currently in `PATH` will be used.
osx-clang (macos-14)
JGit wasn't installed, see above for clues why
osx-clang (macos-14)
perforce wasn't installed, see above for clues why
osx-clang (macos-14)
Already linked: /opt/homebrew/Cellar/gettext/1.0
osx-gcc (macos-14)
JGit wasn't installed, see above for clues why
osx-gcc (macos-14)
perforce wasn't installed, see above for clues why
osx-gcc (macos-14)
Already linked: /opt/homebrew/Cellar/gettext/1.0
osx-reftable (macos-14)
JGit wasn't installed, see above for clues why
osx-reftable (macos-14)
perforce wasn't installed, see above for clues why
osx-reftable (macos-14)
Already linked: /opt/homebrew/Cellar/gettext/1.0
osx-meson (macos-14)
JGit wasn't installed, see above for clues why
osx-meson (macos-14)
perforce wasn't installed, see above for clues why
osx-meson (macos-14)
The following taps are not trusted: aws/tap Homebrew is currently ignoring formulae, casks and commands from these taps because tap trust is required. Untap them with: brew untap aws/tap Trust specific formulae, casks and commands with: brew trust --formula <user>/<tap>/<formula> brew trust --cask <user>/<tap>/<cask> brew trust --command <user>/<tap>/<command> Whole-tap trust is broader and includes all current and future formulae, casks and commands from the listed taps. Trust whole taps with: brew trust aws/tap To disable trust checks: export HOMEBREW_NO_REQUIRE_TAP_TRUST=1 This is not recommended and will be removed in a later release. For more information, see: https://docs.brew.sh/Tap-Trust
osx-meson (macos-14)
Already linked: /opt/homebrew/Cellar/gettext/1.0
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.
win+Meson test (6)
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 (0)
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-linux-breaking-changes
77.2 KB
sha256:9d53b34cb1bd59c00a23a7d09455f4fd189daddafeae08a8836fb4e92ea26146
vs-artifacts-arm64
30.1 MB
sha256:1b9562750e5aef507b553852c0be8baa224cd92bd7ae7a7d82ad1a454f6183d5
vs-artifacts-x64
30.1 MB
sha256:16e70792462620488263829e003975e6ec1a7520464edd0807c69cc1246193d8
windows-meson-artifacts
58.6 MB
sha256:96d1f2c5b4b415f9c98b55af74fde062fe1310e4a020f8b522c09c876d3f4b15