Excerpts from Jan Stancek's message of 2016-05-03 04:43 -04:00:
Is the only criteria that job aborts?
Does it matter how it aborts?
If a test uses rhts-abort, is it going to be re-scheduled as well?
If a task triggers a panic or kernel hangs, jobs aborts. Will that trigger
re-scheduling?
Does it matter when it aborts?
Is failure to install treated in same way as last task hitting EWD?
Very good points Jan.
I wonder if the re-scheduling should follow the same "suspicious abort"
logic we use for broken system detection. That's been changed to and fro
a bit lately, but currently an aborted recipe is suspicious if all tasks
aborted.
So that would include install failures, and EWD due to never starting
the installation -- but would exclude rhts-abort or panics etc (unless
the rhts-abort or panic happens in the very first task, but that's
normally /distribution/install so it shouldn't happen there).
So that means we're not rescheduling aborted recipes, but suspiciously
aborted recipes.
--
Dan Callaghan <dcallagh(a)redhat.com>
Senior Software Engineer, Products & Technologies Operations
Red Hat, Inc.