Federated_Computer/Coredesktop-Dev
3
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Document the smoketest's disk use and how to free it

Browse Source 
The images are kept between runs (installed is about 35 GB), and a
scenario's disk only holds its changes, so the old "a VM disk grows to
about 50 GB and is deleted" was misleading. Mention smoketest clean.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This commit is contained in:
david
2026-11-05 09:14:54 -07:00
co-authored by Claude Opus 5.5
parent ff6b85b439
commit 3117674404
1 changed files with 8 additions and 3 deletions
Download Patch File Download Diff File Expand all files Collapse all files
README.md
+8 -3
View File
@@ -61,9 +61,14 @@ coredesktop-dev smoketest shell installed # SSH into a throwaway VM
```
What it needs: KVM (virtualization turned on in the firmware), about 8 GB of
RAM and 4 CPUs per VM (`SMOKETEST_MEMORY`, `SMOKETEST_CPUS`), and disk space in
`~/.cache/coredesktop-dev/smoketest`: VM disks grow as large as a real install,
about 50 GB, and each run's VM disk is deleted when it's done.
RAM and 4 CPUs per VM (`SMOKETEST_MEMORY`, `SMOKETEST_CPUS`), and about 45 GB
in `~/.cache/coredesktop-dev/smoketest`. The images are kept between runs (the
installed one is the biggest, around 35 GB), along with the shared package
cache and each run's logs. A scenario's own disk only holds its changes to the
image, and is deleted when the scenario ends.
To free space, `coredesktop-dev smoketest clean` deletes old runs' logs, and
`clean --all` deletes everything, so the next run rebuilds the images.
The first run builds two images before any scenario runs: base in a few
minutes, installed in an hour or more. Later runs reuse them.