mirror of
https://github.com/stack-auth/stack.git
synced 2026-06-07 21:04:26 +08:00
7db9fe405e
The stack-cli ignores EMULATOR_IMAGE_DIR / EMULATOR_RUN_DIR and derives
its own paths from STACK_EMULATOR_HOME (or $HOME/.stack/emulator as
default). Without STACK_EMULATOR_HOME set, `emulator start` in CI was
silently auto-pulling from the previous `emulator-dev-latest` release
instead of using the just-built qcow2 + savevm under ${workspace}.
Before: auto-pull got qcow2 + savevm.zst → fast-resume (worked, but
tested the PREVIOUS build, not the current one).
After my capture-locally change: auto-pull only gets qcow2 →
captureLocalSnapshot kicks off a full cold-boot + capture of a stale
image, which is slow and can hang in CI.
Point STACK_EMULATOR_HOME at the workspace so the CLI finds the
just-built images and goes straight to snapshot-resume. Update the
smoke-test job's copy step to target STACK_EMULATOR_HOME so both paths
stay consistent.
|
||
|---|---|---|
| .. | ||
| assets | ||
| recurseml-rules | ||
| workflows | ||
| .recurseml.yaml | ||
| auto_assign.yml | ||
| pull_request_template.md | ||
| SECURITY.md | ||