rename default branch from 'master' to 'main' in refs and test scripts #24474
huangsen365main.yml
on: pull_request
config
5s
fuzz smoke test
2m 20s
static-analysis
5m 22s
sparse
3m 13s
documentation
9m 2s
Matrix: dockerized
Matrix: regular
Matrix: win+VS test
Matrix: win+Meson test
Matrix: win test
Annotations
36 warnings and 22 notices
|
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.
|
|
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
|
|
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
|
|
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 (4)
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 (1)
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 (0)
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.
|
|
win+Meson test (5)
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 (2)
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-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-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-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.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
|
|
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+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+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 (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 (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 (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+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+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 (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 (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 (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+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+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 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 (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
|
|
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 (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 (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 (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 (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
|
Artifacts
Produced during runtime
| Name | Size | Digest | |
|---|---|---|---|
|
windows-artifacts
Expired
|
93.7 MB |
sha256:8eef8fac046a46b5b6207ce9e8e0e3cd8559b144646d32ab91597814651146f7
|
|
|
windows-meson-artifacts
Expired
|
35 MB |
sha256:a424c17134feca309e459d47b00b9daf0d52d69fc2ccf5694de89c979e74075e
|
|