Merge 'readme' into HEAD #5855
dschomain.yml
on: push
config
6s
Matrix: win+VS build
fuzz smoke test
1m 53s
static-analysis
4m 39s
sparse
2m 31s
documentation
9m 5s
Matrix: dockerized
Matrix: regular
Matrix: win+VS test
Matrix: win+Meson test
Matrix: win test
Annotations
36 errors, 40 warnings, and 34 notices
|
linux32 (i386/ubuntu:focal)
Process completed with exit code 1.
|
|
linux32 (i386/ubuntu:focal):
builtin/diff.c#L500
builtin/diff.c:500:3: ignoring return value of 'chdir', declared with attribute warn_unused_result [-Werror=unused-result]
|
|
linux-TEST-vars (ubuntu:20.04)
Process completed with exit code 1.
|
|
linux-TEST-vars (ubuntu:20.04):
builtin/diff.c#L500
builtin/diff.c:500:3: ignoring return value of 'chdir', declared with attribute warn_unused_result [-Werror=unused-result]
|
|
sparse
Process completed with exit code 2.
|
|
linux-breaking-changes (ubuntu:rolling)
Process completed with exit code 1.
|
|
linux-breaking-changes (ubuntu:rolling):
builtin/diff.c#L500
builtin/diff.c:500:17: ignoring return value of ‘chdir’ declared with attribute ‘warn_unused_result’ [-Werror=unused-result]
|
|
static-analysis
Process completed with exit code 1.
|
|
linux-musl-meson (alpine:latest)
Process completed with exit code 1.
|
|
almalinux-8 (almalinux:8)
Process completed with exit code 1.
|
|
debian-11 (debian:11)
Process completed with exit code 2.
|
|
win+Meson test (8)
Process completed with exit code 1.
|
|
linux-reftable (ubuntu:rolling)
Process completed with exit code 1.
|
|
linux-reftable (ubuntu:rolling)
failed: t1517.181 'git survey -h' outside a repository
|
|
linux-sha256 (ubuntu:rolling)
Process completed with exit code 1.
|
|
linux-sha256 (ubuntu:rolling)
failed: t1517.181 'git survey -h' outside a repository
|
|
linux-meson (ubuntu:rolling)
Process completed with exit code 1.
|
|
linux-meson (ubuntu:rolling)
failed: t1517.165 'git survey -h' outside a repository
|
|
win+VS test (1)
Process completed with exit code 1.
|
|
win+VS test (1)
failed: t1517.181 'git survey -h' outside a repository
|
|
win test (1)
Process completed with exit code 1.
|
|
win test (1)
failed: t1517.181 'git survey -h' outside a repository
|
|
osx-clang (macos-13)
Process completed with exit code 1.
|
|
osx-clang (macos-13)
failed: t1517.181 'git survey -h' outside a repository
|
|
osx-gcc (macos-13)
Process completed with exit code 1.
|
|
osx-gcc (macos-13)
failed: t1517.181 'git survey -h' outside a repository
|
|
linux-leaks (ubuntu:rolling)
Process completed with exit code 1.
|
|
linux-leaks (ubuntu:rolling)
failed: t1517.181 'git survey -h' outside a repository
|
|
linux-reftable-leaks (ubuntu:rolling)
Process completed with exit code 1.
|
|
linux-reftable-leaks (ubuntu:rolling)
failed: t1517.181 'git survey -h' outside a repository
|
|
linux-asan-ubsan (ubuntu:rolling)
Process completed with exit code 1.
|
|
linux-asan-ubsan (ubuntu:rolling)
failed: t1517.181 'git survey -h' outside a repository
|
|
osx-meson (macos-13)
Process completed with exit code 1.
|
|
osx-meson (macos-13)
failed: t1517.165 'git survey -h' outside a repository
|
|
osx-reftable (macos-13)
Process completed with exit code 1.
|
|
osx-reftable (macos-13)
failed: t1517.181 'git survey -h' outside a repository
|
|
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
|
|
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>0VTqXaAAAAAAQeRcmaLjIQ7wXpCuyeZsKQ0gxRURHRTIzMDkARWRnZQ==
|
|
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>0VTqXaAAAAABw7quIdZuATZX26xZuhjoIQkwyQUEyMDMwMTA4MDUzAEVkZ2U=
|
|
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 (5)
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.
|
|
win+Meson test (6)
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 (8)
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 (0)
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 (4)
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.
|
|
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.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-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 (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+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 (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 (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+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 (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 (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 (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 (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 (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+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 (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+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+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+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+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+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+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 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+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 (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 (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 (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 (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 (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 (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 (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 (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
|
Artifacts
Produced during runtime
| Name | Size | Digest | |
|---|---|---|---|
|
failed-tests-linux-asan-ubsan
|
25.6 KB |
sha256:1d941c447db38d2e2c65cbc5c5d3a399d5c69a70676aa092f8908064235f8461
|
|
|
failed-tests-linux-leaks
|
25.6 KB |
sha256:6bbde4470f8e8cbeddafd0cf7cb46b81d0f6589a446b55220dd0dc097aa11702
|
|
|
failed-tests-linux-meson
|
25.3 KB |
sha256:1f294db81452a1eb6151d6423e4495b6664581a4b85620403ea406951eb396d8
|
|
|
failed-tests-linux-reftable
|
25.7 KB |
sha256:d407a222bc5edda9b4a5a9e45178c9652a90a7453630572a80f502e3a86f24b0
|
|
|
failed-tests-linux-reftable-leaks
|
25.7 KB |
sha256:a9c055914888f92ad6cf4d499e8ee536625ecb66bf7639c20dd0ce987be202af
|
|
|
failed-tests-linux-sha256
|
25.7 KB |
sha256:00e51487b21fd94a6511e658eed8a730f7a2f6c9bb038c5242b304f35544fd50
|
|
|
failed-tests-osx-clang
|
26.1 KB |
sha256:9560b2debc8a3e6730381ee17ecb5a6674c49c0d9e6a31b517e22e29d647be5b
|
|
|
failed-tests-osx-gcc
|
26.1 KB |
sha256:cc3dddce773926217507d47afd0c9cc335d4b819ed3a364a516c348cbc147286
|
|
|
failed-tests-osx-meson
|
26 KB |
sha256:22acb08763e659710db098858d1aa830112dd3a66dcc9298c1ef042c11d29edf
|
|
|
failed-tests-osx-reftable
|
26.3 KB |
sha256:c33377263bef48d554a01e69e4d0eba55fb37c40273cf7ef955866e7411ea167
|
|
|
failed-tests-windows-1
|
25.6 KB |
sha256:4b2e47a4891a59a8b7e8382a9828599c1ea02a140420f6b52450732e16f8281a
|
|
|
failed-tests-windows-vs-1
|
26 KB |
sha256:96ba5523187dc19cd1eead047372a8dc745342db0910f755b57ae7726ea0dffe
|
|
|
vs-artifacts-arm64
|
27.8 MB |
sha256:fe88660d4884ce2c913dc9d5c51d4e6cc7a760f916c4f8dffbbc529873e1283b
|
|
|
vs-artifacts-x64
|
28.8 MB |
sha256:d7ad8a23ea088d7462463695881c440b02122ae370e36e6de56e7578923b50fd
|
|
|
windows-artifacts
|
98.9 MB |
sha256:7a7ae59f3c28565ab1ef2ac23942fce9252fe5da5114ed26920b5e81c980d35a
|
|
|
windows-meson-artifacts
|
35.5 MB |
sha256:da8a806118c042b625e5d8ef7c0569d8aedb03dc56cd38071cb7637a42f2c6a8
|
|