Infer categorized watcher group names from actual host execution

- update the watcher to stop trusting misleading categorized child build labels when they do not match the host/spec actually being executed
- infer the reported categorized group name from the actual host being run, so mismatched labels like ubuntu-batch for a Red Hat host are corrected in status reporting
- document the categorized watcher workaround in the ATVM guide, watcher design, and watcher README without changing the underlying ATVM runner scripts
This commit is contained in:
2026-03-26 14:20:22 -04:00
parent 7d49896ac2
commit f5eb21cccd
4 changed files with 49 additions and 5 deletions

View File

@@ -44,6 +44,7 @@ A categorized run must be treated differently:
- then continue watching for the next grouped sub-run
- the watcher must remain alive while the parent categorized request or related child Cypress process is still active
- one completed grouped sub-run must not be treated as proof that the parent categorized request is finished
- if the child build id label does not match the actual host/spec being executed, the watcher must infer the real group from host execution and use that inferred group for reporting
- the watcher must not wait until the very end to send one single parent-only post
Evidence sources: