Problem
listLmStudio: nonzero exit integration test fails intermittently in CI (Node 20). The test asserts both ls --llm --json and ps --json appear in the argv log, but when lms exits nonzero, Promise.all rejects as soon as ls fails. The ps call (which has .catch()) may or may not have written to the log yet — it's a race condition.
Fix
Only assert that ls --llm --json was called. The ps call is best-effort by design (it has .catch() in the production code), so its presence in the argv log is non-deterministic on failure paths.
PR
#22
Problem
listLmStudio: nonzero exitintegration test fails intermittently in CI (Node 20). The test asserts bothls --llm --jsonandps --jsonappear in the argv log, but whenlmsexits nonzero,Promise.allrejects as soon aslsfails. Thepscall (which has.catch()) may or may not have written to the log yet — it's a race condition.Fix
Only assert that
ls --llm --jsonwas called. Thepscall is best-effort by design (it has.catch()in the production code), so its presence in the argv log is non-deterministic on failure paths.PR
#22