Fix M10 timing trace failure handling
Foundation / checks (deploy) (push) Successful in 5s
Foundation / checks (ecs) (push) Successful in 2m1s
Foundation / checks (postgres) (push) Canceled after 0s
Foundation / checks (tsan) (push) Canceled after 0s
Foundation / postgres-tools (push) Canceled after 0s
Foundation / server-image (push) Canceled after 0s
Foundation / image (push) Canceled after 0s
Foundation / checks (checks) (push) Canceled after 6m59s
Foundation / checks (network) (push) Canceled after 4m46s
Foundation / checks (client) (push) Canceled after 7m4s

This commit is contained in:
dingo
2026-10-03 21:43:15 -04:00
parent 7956143cd8
commit db19e0bb85
3 changed files with 47 additions and 8 deletions
+15
View File
@@ -4150,3 +4150,18 @@ format check; Windows MSVC 19.44 preset `quic` build and CTest 4/4 (binary rebui
timestamp checked).
Not done: wiring into evo-server and the engineering client, the durable control lease
(10.3c), an impairment-relay run of the login path.
## 2026-10-03 — M10.1 trace safety corrections
The trace runner now requires a new output directory, creates it with owner-only
permissions, and leaves existing paths untouched. A rejected intention now makes
`evo-dev-session trace` return failure; the runner records each local run's status and
fails the experiment if any run fails.
Executed: GCC 13 Linux Release build of `evo-dev-session` in an isolated
`build/network-wsl` directory; network CTest 1/1; clang-format-19 check for the changed
C++ file; Bash syntax check; temporary-directory check confirmed an existing output
directory is refused and its marker file preserved. `git diff --check` passed.
Not done: no end-to-end trace against a server deliberately configured to reject an
intention; no Docker/Gitea run. The return path is compile-checked but rejection is not
covered by a dedicated application integration test.