8 Commits

Include renames

Author	SHA1	Message	Date
davidandClaude Opus 5.5	0950625536	smoketest: install the baselines with herdr-bin for herdr ... Every baseline installs herdr from source, which pins zig 0.16, and Arch now has 0.17, so their installs fail. Install them with herdr-bin (which provides herdr, and is what HEAD installs) in a commit on top, then put the clone back at the baseline itself, since update pulls --ff-only. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>	2026-11-05 10:49:35 -07:00
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	101261bd9b	update: a failing hook without run_update fails the update ... Since a65f07c ran each hook in a subshell, a hook that does its work as it's sourced (12-migrations, 15-services, 20-aur, 30-flatpak and others) had its failure lost: the run_update check after source left the subshell's status at 0, so update said "Done." and exited 0. The smoketest's 40-failing-migration caught it. update now exits the subshell with the sourced hook's status. Also, the smoketest scenarios that check whether a migration ran look for "Running migration " so install.sh's "Running migrations..." heading doesn't match (11-refresh failed on it). Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>	2026-11-05 08:39:54 -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 ... 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	5ed3df55e3	further checks	2026-11-04 10:05:50 -07:00
david	2b85af286f	testing harness, coredesktop-dev	2026-11-04 09:39:46 -07:00