Skip to content

2026.8.26.1 — naming the host's own target changed the link line #19

2026.8.26.1 — naming the host's own target changed the link line

2026.8.26.1 — naming the host's own target changed the link line #19

Triggered via pull request August 26, 2026 00:22
Status Failure
Total duration 15m 17s
Artifacts 4

ci-target-matrix.yml

on: pull_request
Matrix: invariants
Matrix: scan
coverage (every host the table names was scanned)
5s
coverage (every host the table names was scanned)
Fit to window
Zoom out
Zoom in

Annotations

34 errors and 9 warnings
scan (linux-aarch64)
[payload] linux-aarch64 x86_64-windows-gnu gcc@16.1.0 → unsupported, and the expected table does not mention this cell
scan (linux-aarch64)
[payload] linux-aarch64 x86_64-none-elf gcc@16.1.0 → unsupported, and the expected table does not mention this cell
scan (linux-aarch64)
[payload] linux-aarch64 x86_64-macos gcc@16.1.0 → unsupported, and the expected table does not mention this cell
scan (linux-aarch64)
[payload] linux-aarch64 x86_64-linux-musl gcc@16.1.0 → mismatch, and the expected table does not mention this cell
scan (linux-aarch64)
[payload] linux-aarch64 riscv64-none-elf gcc@16.1.0 → unsupported, and the expected table does not mention this cell
scan (linux-aarch64)
[payload] linux-aarch64 riscv64-linux-musl gcc@16.1.0 → unsupported, and the expected table does not mention this cell
scan (linux-aarch64)
[payload] linux-aarch64 riscv32-none-elf gcc@16.1.0 → unsupported, and the expected table does not mention this cell
scan (linux-aarch64)
[payload] linux-aarch64 aarch64-none-elf gcc@16.1.0 → unsupported, and the expected table does not mention this cell
scan (linux-aarch64)
[payload] linux-aarch64 aarch64-linux-musl gcc@16.1.0 → ok, and the expected table does not mention this cell
scan (linux-aarch64)
[payload] linux-aarch64 aarch64-linux-gnu gcc@16.1.0 → unsupported, and the expected table does not mention this cell
scan (macos-arm64)
[payload] macos-arm64 x86_64-none-elf llvm@22.1.8 → ok, and the expected table does not mention this cell
scan (macos-arm64)
[payload] macos-arm64 x86_64-macos llvm@22.1.8 → unsupported, and the expected table does not mention this cell
scan (macos-arm64)
[payload] macos-arm64 x86_64-linux-musl llvm@22.1.8 → unsupported, and the expected table does not mention this cell
scan (macos-arm64)
[payload] macos-arm64 riscv64-none-elf llvm@22.1.8 → ok, and the expected table does not mention this cell
scan (macos-arm64)
[payload] macos-arm64 riscv64-linux-musl llvm@22.1.8 → unsupported, and the expected table does not mention this cell
scan (macos-arm64)
[payload] macos-arm64 riscv32-none-elf llvm@22.1.8 → ok, and the expected table does not mention this cell
scan (macos-arm64)
[payload] macos-arm64 aarch64-none-elf llvm@22.1.8 → ok, and the expected table does not mention this cell
scan (macos-arm64)
[payload] macos-arm64 aarch64-macos llvm@22.1.8 → ok, and the expected table does not mention this cell
scan (macos-arm64)
[payload] macos-arm64 aarch64-linux-musl llvm@22.1.8 → unsupported, and the expected table does not mention this cell
scan (macos-arm64)
[payload] macos-arm64 aarch64-linux-gnu llvm@22.1.8 → unsupported, and the expected table does not mention this cell
scan (windows-x86_64)
[payload] windows-x86_64 riscv64-linux-musl
scan (windows-x86_64)
[payload] windows-x86_64 riscv64-linux-musl
scan (windows-x86_64)
[payload] windows-x86_64 riscv32-none-elf
scan (windows-x86_64)
[payload] windows-x86_64 riscv32-none-elf
scan (windows-x86_64)
[payload] windows-x86_64 aarch64-none-elf
scan (windows-x86_64)
[payload] windows-x86_64 aarch64-none-elf
scan (windows-x86_64)
[payload] windows-x86_64 aarch64-linux-musl
scan (windows-x86_64)
[payload] windows-x86_64 aarch64-linux-musl
scan (windows-x86_64)
[payload] windows-x86_64 aarch64-linux-gnu
scan (windows-x86_64)
[payload] windows-x86_64 aarch64-linux-gnu
coverage (every host the table names was scanned)
Process completed with exit code 1.
coverage (every host the table names was scanned)
'windows-x86_64' was scanned and the expected table does not mention it
coverage (every host the table names was scanned)
'macos-arm64' was scanned and the expected table does not mention it
coverage (every host the table names was scanned)
'linux-aarch64' was scanned and the expected table does not mention it
invariants (macos-arm64)
Node.js 20 is deprecated. The following actions target Node.js 20 but are being forced to run on Node.js 24: actions/cache@v4, actions/checkout@v4. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
invariants (linux-x86_64)
Node.js 20 is deprecated. The following actions target Node.js 20 but are being forced to run on Node.js 24: actions/cache@v4, actions/checkout@v4. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
invariants (windows-x86_64)
Node.js 20 is deprecated. The following actions target Node.js 20 but are being forced to run on Node.js 24: actions/cache@v4, actions/checkout@v4. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
invariants (linux-aarch64)
Node.js 20 is deprecated. The following actions target Node.js 20 but are being forced to run on Node.js 24: actions/cache@v4, actions/checkout@v4. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
scan (linux-aarch64)
Node.js 20 is deprecated. The following actions target Node.js 20 but are being forced to run on Node.js 24: actions/cache@v4, actions/checkout@v4, actions/upload-artifact@v4. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
scan (macos-arm64)
Node.js 20 is deprecated. The following actions target Node.js 20 but are being forced to run on Node.js 24: actions/cache@v4, actions/checkout@v4, actions/upload-artifact@v4. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
scan (windows-x86_64)
Node.js 20 is deprecated. The following actions target Node.js 20 but are being forced to run on Node.js 24: actions/cache@v4, actions/checkout@v4, actions/upload-artifact@v4. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
scan (linux-x86_64)
Node.js 20 is deprecated. The following actions target Node.js 20 but are being forced to run on Node.js 24: actions/cache@v4, actions/checkout@v4, actions/upload-artifact@v4. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
coverage (every host the table names was scanned)
Node.js 20 is deprecated. The following actions target Node.js 20 but are being forced to run on Node.js 24: actions/checkout@v4, actions/download-artifact@v4. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/

Artifacts

Produced during runtime
Name Size Digest
matrix-linux-aarch64
385 Bytes
sha256:24f9cfc6004d36df3136c7cc865a2a7da65da1382529325c5fc43d149ad034c4
matrix-linux-x86_64
606 Bytes
sha256:8ee83161222bdfc400164b083de4062218594fbe924b4865f5f5d1f4fa427992
matrix-macos-arm64
487 Bytes
sha256:2ea4969cbf1e2cd3757260921f84675dc66bb889dc30da0849707b7b7beeffab
matrix-windows-x86_64
557 Bytes
sha256:a8afc6393431fcf2e328d3a8c49b451dd990201bf469c86333759cf03b94b61c