On 22.1.2014 02:50, Nick Coghlan wrote:
Another one from the "notable merges" files is Dan
to add the ability to automatically detect installer failures from the
console log output and abort the recipe immediately rather than waiting
for the external watch dog to time out:
This feature will be part of the upcoming 0.15.3 release, and should
result in faster feedback cycles for anyone working on installer issues,
as well as reducing the time consumed on systems when attempting to test
against trees that contain a broken installer version.
nice feature! Can Beaker provide the user with an error message in
addition to the usual status & result?
IMO it would be much better to tell the user e.g. "abort/fail - anaconda
in interactive mode" instead of just "abort/fail". Especially since
Beaker already has this information (even if only in the form of
testsuite test-case names).
Motivation: I often struggle with making users debug failed
installations. They perceive it as part of the infrastructure, not the
system under test = someone else's problem. Any info that gives them
more insight into why their jobs failed helps.