feat: plan schema 9, a scenario's cache: driver cold, driver warm or cold starts #99
No reviewers
Labels
No labels
kind
bug
kind
chore
kind
docs
kind
feature
kind
performance
kind
question
priority
critical
priority
high
priority
low
risk
high
risk
low
risk
medium
status
blocked
status
confirmed
status
duplicate
status
invalid
status
needs-info
status
wontfix
ci: approved
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set
Reference
MagicBeanDev/Beanstalk!99
Loading…
Reference in a new issue
No description provided.
Delete branch "HumanBean/Beanstalk:feat/cache-states"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
A PR about a first start needs to know what the start's caches hold, and a plan couldn't say. Plans for Longshot #1701 (the ASTC converters on a first start), #1450 (a second start reusing the first's cache) and #426 (an empty shader cache) each said so.
Stacked on #98 (schema 8). Its commit is in this branch until #98 merges; merge #98 first.
What changed
A scenario's
cache(plan schema 9):cachecache/as_is(default)driver_colddriver_warmcoldXDG_CACHE_HOME), so main and the PR never share one.driver_warmkeeps one home per scenario, launch group, side and build variant (runs/homes/...).driver_cache_start_mb, read from the game'svk: driver shader cache at the start: N MBline. Adriver_coldorcoldrun that found a cache is an error.skipped. The planner is told to targetlinuxfor them.driver_warm's extra start per side, and about 10 more minutes for eachcoldstart.test-plan.md,protocol.md) describe it.No screenshots: nothing on screen changes beyond the plan's words.
Testing
python -I agent/tests/test_agent_core.py --strict: 2157 checks passed. New fixtures (cache-states.toml,cache-cold.toml,cache-as-is.toml,bad-cache-schema.toml,bad-cache-value.toml) are cross-checked against the coordinator's reader. New runner checks use a capturing sandbox:coldstart finds no game cache, and the cache is put back afterwards;driver_warm's first start is the unmeasured one, in the side's kept home;driver_coldgets a new home;pytest -qincoordinator/: 589 passed, 1 skipped. Twotest_public_pulls.pytests failed once on timing and passed when run again; they aren't touched here.coldstart's pipeline preparation time and adriver_warmstart actually hitting the kept cache.🤖 Generated with Claude Code