On 22.1.2014 23:20, Dan Callaghan wrote:
Excerpts from Ales Zelinka's message of 2014-01-22 22:16:46
+1000:
> 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).
Yes, we do record the failure message in the recipe results. I would
like to improve the way we show installation status/progress [1] but in
the meantime, if Beaker detects installation failure it will be recorded
as a Fail result against the first task (typically
/distribution/install) with a message such as:
nice!
Installation failed: + Error Parsing Kickstart Config +
Some of the failure messages are unfortunately a bit more cryptic, like:
Installation failed: Press enter to exit.
hmm, that might confuse users more
than no error message. I'll probably
display just some generic "fatal error in anaconda log" message for all
the "Installation failed:.*" strings.
If you're interested in seeing the myriad ways in which Anaconda can
report a failure, I collected some samples [2] when I implemented the
feature. So the heuristics for finding failures are a bit crude...
[1]
https://bugzilla.redhat.com/show_bug.cgi?id=991245
[2]
http://fedorapeople.org/~dcallagh/bz952661-anaconda-failures/
Hehe, yeah. I saw the patterns and example logs in the patch. That will
be fun to keep up to date.
--
Ales
Platform BU, BaseOS QE - Daemons