Red Hat Bugzilla – Bug 851897
recipe's watchdog status grouped by recipe_set
Last modified: 2014-12-07 20:13:30 EST
In a multi-recipe recipeset, the status of any recipe is potentially determined by the status of another recipe in the same recipeset.
It seems this was introduced in 9902b2315d217190a2e508e2dbad18adcc3aeb29.
and recently caused this problem 849818.
Do we still need to group by recipeset id for beaker-watchdog?
Bulk reassignment of issues as Bill has moved to another team.
I suspect this is for multi-host tests, so that the external watchdog does not kick in so long as at least one recipe is still alive and working.
Is there any compelling reason why we should change this, apart from bug 849818 which is now fixed?
No, this can be closed