Refine categorized timing metrics and coverage output
This commit is contained in:
@@ -321,6 +321,14 @@ This file stores run-specific examples only when a run produced a new learning r
|
||||
- Store and display the exact `cmc-templates.py` command in `NOTES:`.
|
||||
- Omit only the outer remote-execution wrapper.
|
||||
|
||||
## Run Learning: 2026-03-27 (Avoid redundant categorize flags and infer grouped timing stats)
|
||||
- Observed requirement:
|
||||
- When `categorize mode: enabled` is already shown in `COVERAGE:`, repeating `--categorize` under `run options` is redundant.
|
||||
- Grouped categorized results should still show `quickest`, `longest`, and `average` when those values can be inferred from recovered host timing.
|
||||
- Action for future runs:
|
||||
- Do not repeat `--categorize` under `run options` when categorize mode is already shown separately.
|
||||
- When grouped host results are reconstructed from reporter artifacts, infer per-host durations from the recovered host timestamp sequence and grouped end time so grouped timing stats do not default to `n/a` unnecessarily.
|
||||
|
||||
## Run Learning: 2026-03-27 (Do not auto-add blacklist excludes for explicitly specified VMs)
|
||||
- Observed requirement:
|
||||
- When the operator explicitly specifies the VM or VM list to run, they do not want the maintained `--exclude_partial_match` blacklist added automatically.
|
||||
|
||||
Reference in New Issue
Block a user