| Commit message (Collapse) | Author | Age | Files | Lines | |
|---|---|---|---|---|---|
| * | fix(test): pin stdin so the net-scenario harness stops hanging | Craig Jennings | 20 hours | 1 | -0/+6 |
| | | | | | | | The stubbed ssh is `cat >/dev/null`, which drains stdin to EOF. Without an explicit stdin the stub inherits whatever the test runner had, so it returned instantly when stdin was redirected and blocked forever when it was a terminal or a live pipe. All five tests then hit their 20-second timeout. That made the suite unreliable in the case that matters most, running it by hand. `make test-unit </dev/null` passed while the same target run from a terminal failed, which reads as a flaky test rather than an environment-dependent one. | ||||
| * | fix(test): count a diagnose miss as a failed net scenario | Craig Jennings | 2026-07-20 | 1 | -0/+102 |
| The scenario_diagnose_expect else-branch printed its FAIL line but never forced a non-zero subshell exit. A scenario whose only failure was the diagnose check counted as passed, so the run printed "all scenarios passed" and exited 0 over a real net-doctor diagnosis regression. The miss now sets a per-scenario rc that carries to the subshell exit. The fix and assert still run first, since the repair result is worth having either way. The new harness drives the real script with stubbed ssh/rsync/jq and a controllable fake scenario, pinning all four check outcomes. | |||||
