Skip to content

0.23.0 --- an image at its base; exec regions zero, sealed and mapped… #266

0.23.0 --- an image at its base; exec regions zero, sealed and mapped…

0.23.0 --- an image at its base; exec regions zero, sealed and mapped… #266

Re-run triggered November 2, 2026 23:20
Status Success
Total duration 2m 2s
Artifacts –

ci.yml

on: push
Matrix: conformance
Matrix: declarations
Matrix: substitution
Fit to window
Zoom out
Zoom in

Annotations

12 warnings and 2 notices
substitution holds (gcc@16.1.0)
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. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
conformance (openkal-windows, msvc@system)
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. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
conformance (openkal-linux, gcc@16.1.0)
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. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
conformance (openkal-macos, llvm@20.1.7)
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. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
declarations (windows-2022, msvc@system)
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. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
declarations (windows-2022, llvm@20.1.7)
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. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
substitution holds (llvm@22.1.8)
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. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
declarations (macos-15, llvm@20.1.7)
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. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
conformance (openkal-windows, llvm@20.1.7)
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. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
declarations (ubuntu-24.04, llvm@22.1.8)
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. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
conformance (openkal-linux, llvm@22.1.8)
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. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
declarations (ubuntu-24.04, gcc@16.1.0)
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. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
conformance (openkal-macos, llvm@20.1.7)
Due to capacity constraints, jobs targeting macOS arm64 runners may experience longer queue times.
declarations (macos-15, llvm@20.1.7)
Due to capacity constraints, jobs targeting macOS arm64 runners may experience longer queue times.