Commit Graph
5 Commits
Author SHA1 Message Date
davidandClaude Opus 5.5 a2468c50f1 smoketest: send gitea.federated.computer/david's URL to the fake upstream too
install.sh at every baseline in smoketest/baselines clones from
https://gitea.federated.computer/david/coredesktop.git, which wasn't in
COREDESKTOP_URLS. So 30-upgrade-from-baseline installed today's real
upstream (via Gitea's redirect) instead of the baseline, and failed when
the old install.sh asked for files that have since gone.

Add a test that every URL install.sh has ever cloned from is in the list.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-11-05 10:48:06 -07:00
davidandClaude Opus 5.5 6524ff9efd smoketest: say once a minute that a command in the VM is still running
run_in_vm prints how long it has run and the log's latest line, so an
hour-long install.sh shows progress without tail -f.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-11-05 08:36:01 -07:00
davidandClaude Opus 5.5 7ae6a5c1be smoketest: don't run the pre-push hook when pushing to the VM
shellcheck / shellcheck (push) Failing after 16s
upstream_set pushes the commit under test from the working copy, so
coredesktop-dev's pre-push hook ran make check on every push to the VM.
Inside the smoketest those checks saw VM_GIT_URL and friends, the
smoketest tests pushed to the real VM and failed, and the hook stopped
the push, failing the installed image's build. The push now uses
--no-verify, and the tests clear the smoketest's variables.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-11-05 07:31:55 -07:00
davidandClaude Opus 5.5 523c5b9b15 smoketest: write run_in_vm's log as the command runs
So a long command (install.sh takes an hour or more) can be followed with
tail -f; run_in_vm prints the log's path when it starts.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-11-05 07:28:10 -07:00
david 2b85af286f testing harness, coredesktop-dev
shellcheck / shellcheck (push) Failing after 17s
2026-11-04 09:39:46 -07:00