diff options
| author | user <user@clank> | 2026-09-12 16:06:02 +0200 |
|---|---|---|
| committer | user <user@clank> | 2026-09-12 16:06:02 +0200 |
| commit | 3887858082dfcdc23a368a69f0ee7c6eb74a1759 (patch) | |
| tree | 1c43ea96cf19e47f2010e60a008f13bd7d61a603 /docs/panes.md | |
| parent | vendor: the wuffs calloc stub was hijacking the demo's allocator (diff) | |
| download | slosh-3887858082dfcdc23a368a69f0ee7c6eb74a1759.tar.gz slosh-3887858082dfcdc23a368a69f0ee7c6eb74a1759.tar.xz slosh-3887858082dfcdc23a368a69f0ee7c6eb74a1759.zip | |
web: boot the demo before publishing it
v0.1.7 shipped a demo that could not start a session, and the site was
live and broken because nothing between `make` and `rsync` ever ran the
guest. The demo is the one artifact here whose build succeeding says
nothing about it working: it is a cross-compiled riscv64 binary in an
ext2 image, so the failures the rest of build-site would notice -- a
compiler error, a missing file -- are not where its failures live. A
guest that segfaults on startup links, packages and copies perfectly,
and the page then loads, draws a terminal and sits there dead.
web/demo/boot-check already boots that exact image in a native emulator
and fails if init does not reach a composed screen. It took twenty
seconds to find what the browser reported as one unexplained line, so
it runs in the build now, between `make site` and the copy into the
staging tree. NO_BOOT_CHECK=1 opts out; NO_DEMO=1 skips it with the
rest of the demo.
Diffstat (limited to 'docs/panes.md')
0 files changed, 0 insertions, 0 deletions
