4493b14647
The depth-first walk killed the child install.ps1 was waiting on and only then the root, which races the leader's own reaction to that death. It is not a theoretical race: in staging run 30424366953 install.ps1 had already printed "unsloth studio setup failed (exit code -1)" by the time Stop-Process reached it. A leader that wins the race makes Stop-Process throw, and the new root-kill assertion would then fail a leg whose interruption the driver really did deliver. The tree is now snapshotted first, since a dead parent leaves nothing to walk, then the root goes down ahead of its descendants. A dead leader cannot react to a child and cannot respawn one either, which is what the depth-first order was for. |
||
|---|---|---|
| .. | ||
| agent-guides-drive.sh | ||
| agent-guides-install.sh | ||
| assert-llama-loads.sh | ||
| assert-prompt-cache.sh | ||
| ci-connect-prompt.txt | ||
| ci-min-system-prompt.txt | ||
| hf-download-with-retry.sh | ||
| interrupt-install.ps1 | ||
| interrupt-install.sh | ||
| interrupted_install_probe.py | ||
| run-studio-permission-browser.sh | ||
| serve-unsloth-run.sh | ||