I'm not sure what you mean, but if you're refering to the "Build FAILED"
messages like here
then it does not mean, that the build of the package failed. Just that the tested update
consists of several builds, and for each one, we log whether the build passed or failed
the depcheck test.
Then if at least one of the builds from the update fails the depcheck test, the whole
depcheck run is marked as Failed.
But maybe I misunderstood, what you mean.
----- Original Message -----
From: "Adam Williamson" <awilliam(a)redhat.com>
To: "AutoQA development" <autoqa-devel(a)lists.fedorahosted.org>
Sent: Friday, February 3, 2012 3:45:20 AM
Subject: Re: ResultsDB is up'n'running on staging
On Thu, 2012-02-02 at 11:12 -0500, Josef Skladanka wrote:
> Hi gang,
> kudos to Petr for bug-fixing on the fly today.
> *insert fireworks*
> *insert more fireworks*
A small thought: it seems a lot of depcheck tests 'fail' because the
build of the package itself failed. That's not really a depcheck
failure, it's more of a null result, or something. Could this kind of
'couldn't even get to the point of running the test' failure be
displayed differently from a 'test ran and failed' failure?
Fedora QA Community Monkey
IRC: adamw | Twitter: AdamW_Fedora | identi.ca: adamwfedora
autoqa-devel mailing list