[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: "Always failed" ? Doesn't seem to be true


On 20-06-18 01:00, Ian Jackson wrote:
> I happened to look at
>   https://ci.debian.net/packages/d/dgit/testing/amd64/
> and noticed that there is a version of git which breaks something in
> dgit or dgit's test suite.
> It says "This package is failing and has 5.0 passed." but the package
> is not failing.

Well, the last run failed, didn't it? This page (testing) of ci.d.n is
not compatible with how it's used. I.e. this page just reports the
status of the last test that gets processed during the generation of the
page (which is in > 95% of cases the top one). I think that for testing,
we should remove this text.

> In
>   https://qa.debian.org/excuses.php?package=git
> it says
>   * autopkgtest for dgit/4.4: amd64: Always failed
> But actually my tests pass in testing.

I am afraid there is a bug in britney somewhere in the case it never
ever generated a migration-reference/0 trigger for a package (it does
that only when it find no previous results at all). The idea is (but
apparently it doesn't properly work in that case) is that the internal
reference in britney is build up by previous results.

I triggered a migration-reference/0 on britneys behalf. Git should get a
10 days additional age on top of the 5 days by default.

It was on my list (but I'll put it higher) to trigger
migration-reference/0 for ALL packages that have autopkgtest if there is
no such trigger in the last month and put that in cron.

> What is going on, please ?

See above.

The wording of "Always failed" is misleading anyways, that was copied
from Ubuntu. We should update that to "Fails in baseline".

A side note: for urgency high or higher, the results for autopkgtest are


Attachment: signature.asc
Description: OpenPGP digital signature

Reply to: