mirror of
https://github.com/stablyai/orca.git
synced 2026-09-28 08:02:43 +00:00
Neil
065b3fab24
Both were found running the four `*.wsl.test.ts` suites against a live
Ubuntu-24.04 distro — the first time any of them had executed.
Lane ratchet header, next to the existing "does a registered suite EXECUTE"
prose, because that is where someone will look:
- nothing in `.github/` or `config/` sets any `ORCA_REAL_WSL_*` variable, so
all four suites ran on no machine until exported by hand. They pass; that
was not knowable from a green board.
- these gates are compared with `===`, and `set VAR=1 && cmd` in cmd.exe
stores `"1 "`. Trailing space, gate shut, and the suite reports "skipped"
exactly as it does when the variable was never set. I filed that as a repo
defect for several minutes before checking my own shell. A gate whose closed
state is indistinguishable from its unset state is a gate nobody is running.
- registered, triggered, and unable to fail are three separate ways to be
invisible. The banner suite was all three at once.
Runner suite header: it appends `sleep 60` to the shared distro user's
`~/.profile` and backs up to a fixed path with `|| true`, whose teardown
fallback is `rm -f "$HOME/.profile"`. The teardown works — it has no margin.
An aborted run leaves every new login stalling a minute, or deletes the profile.
The note says not to run it against a shared distro, and gives the check to
repeat if you must: hash `$HOME/.profile` either side, never assume the restore.
Comments only; no assertion or behaviour changes. Both lane ratchets stay green.