Skip to content

fix(viewer): recover screen maps created after setup() (#250) #21

fix(viewer): recover screen maps created after setup() (#250)

fix(viewer): recover screen maps created after setup() (#250) #21

Triggered via pull request September 17, 2026 19:46
Status Success
Total duration 4m 45s
Artifacts –

linux-x86-terminal-test.yml

on: pull_request
Fit to window
Zoom out
Zoom in

Annotations

3 warnings and 1 notice
call / terminal-test
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, astral-sh/setup-uv@v5. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
call / terminal-test
soldr cook prebuilt dependencies, but this job's compile cache recorded 362 miss(es) and 0 hit(s) — none of the cooked artifacts were reused. This usually means the job compiled under a different rust toolchain or profile than setup-soldr's cook (for example a nightly dylint/driver pass). cook cannot warm a different-toolchain compile; rely on the build-cache layer there, or set prebuild-deps: none to skip the unused cook.
call / terminal-test
setup-soldr: build-cache cache payload is 1.11GB before compression (>512.0MB). Largest files: zccache/private/soldr-dev-3a200690d18344ce/artifacts/aa7fb7956243aadc9a3dd5e7b627c8046f474f95ac7a96c096b36112646d279f_0 (50.8MB), zccache/private/soldr-dev-3a200690d18344ce/artifacts/0a6351f4413513fb1fbaff8a12e0d0f8e83d94ade821d780ffca0f478cea814c_0 (37.8MB), zccache/private/soldr-dev-3a200690d18344ce/artifacts/186c9eb267e169cacfa9263140d231ec346dd2bcc32f27dead176920eb0f5e88_0 (34.7MB), zccache/private/soldr-dev-3a200690d18344ce/artifacts/aa7fb7956243aadc9a3dd5e7b627c8046f474f95ac7a96c096b36112646d279f_2 (31.6MB), zccache/private/soldr-dev-3a200690d18344ce/artifacts/268f42cccb9edf0510e5520a3181b1bce9a5424cf3a94de0702995cdc6219c59_0 (28.7MB)
call / terminal-test
setup-soldr: target/ already has compiled artifacts (from `soldr cook`). target-cache is disabled, so this is the current run's own output and is expected - no action needed. (Enable target-cache and you'd get the stale-rust-plan warning instead.)