----- Original Message -----
From: "Róman Joost" <rjoost(a)redhat.com>
To: "Beaker Public" <beaker-devel(a)lists.fedorahosted.org>
Cc: "Bruno Goncalves" <bgoncalv(a)redhat.com>
Sent: Tuesday, 3 May, 2016 3:31:28 AM
Subject: [Beaker-devel] RFC: Design proposal for a re-scheduling capability of recipe
I'd like to share a new design proposal which hopefully addresses some
of the issues people have when larger jobs fail because of broken
Kudos to Bruno Goncalves who brought it initially to my attention.
Is there something the proposal misses? Are there perhaps details which
are not correctly flashed out? Do you have questions?
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?
> Kind Regards,
> Róman Joost
> Software Engineer, PnT DevOps - Developer (Brisbane)
> email: rjoost(a)redhat.com | tz: UTC+10 | GPG ID: 0xBE2B559D at pgp.mit.edu
> irc: #beaker #tps-devel
> Beaker-devel mailing list