Skip to content

ci: render the real WASM viewer on Linux and fail on a blank canvas #233

ci: render the real WASM viewer on Linux and fail on a blank canvas

ci: render the real WASM viewer on Linux and fail on a blank canvas #233

Triggered via pull request September 17, 2026 20:34
Status Success
Total duration 8m 12s
Artifacts –

linux-x86-dwarf-smoke.yml

on: pull_request
Fit to window
Zoom out
Zoom in

Annotations

2 warnings and 1 notice
dwarf-smoke
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/setup-node@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/
dwarf-smoke
soldr cook prebuilt dependencies, but this job's compile cache recorded 3 miss(es) and 0 hit(s) — none of the cooked artifacts were reused. cook ran with prebuild-deps-flags='--release' (release profile), but cargo check/clippy/doc/test compile in the dev (debug) profile, which is a different cache key. Set prebuild-deps-flags: "" to cook in the debug profile so this job reuses it, or prebuild-deps: none if the job compiles under a different toolchain (build-cache still carries that work across runs).
dwarf-smoke
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.)