Simplify ATVM host detail reporting
This commit is contained in:
@@ -665,3 +665,12 @@ This file stores run-specific examples only when a run produced a new learning r
|
||||
- Action for future runs:
|
||||
- When a run is marked `FAILED` from hang-kill markers or non-zero runner exit and no host results are available, synthesize one failed host row from current host/spec inference.
|
||||
- Use a clear failure detail such as `hang timeout killed runner` so operator-facing status always includes a concrete host failure line.
|
||||
|
||||
## Run Learning: 2026-06-04 (Host detail should not show total test counts)
|
||||
- Observed failure mode:
|
||||
- A passing compute-migration run posted `29 tests, 0 failures` in the `HOSTS` detail column while `TEST FLOW:` listed 30 planned/generated spec steps.
|
||||
- The mismatch was confusing because host detail came from actual Cypress reporter counts, while `TEST FLOW:` came from static generated-spec extraction.
|
||||
- Action for future runs:
|
||||
- Keep raw test/failure counts in watcher state for classification and debugging, but do not render them in the `HOSTS` detail column.
|
||||
- For passing hosts, render detail as `completed`.
|
||||
- For failed hosts, render only the failing step plus compact error summary; put richer excerpts in `FAILURE NOTES:`.
|
||||
|
||||
Reference in New Issue
Block a user