On Sun, May 17, 2015 at 08:13:01AM +0100, Neil Williams wrote:
> On Sat, 16 May 2015 21:23:25 +0200
> Ole Streicher <olebole@debian.org> wrote:
>
> > Hi,
> >
> > how does ci.debian.net actually (re-)run the tests?
>
> I'm also seeing problems with updated packages not running the tests.
> The News item on ci.debian.net only lists a handful of packages being
> tested per day. With the churn through unstable after the release, I
> would have expected this to be higher.
The "News" box at the homepage only lists state changes, i.e. a package
that used to fail now passes, or the other way around ("no news is good
news")
> I've made a range of uploads for packages which have been running
> autotests previously but two of these packages have not been tested
> since the upload and have now migrated to stretch. One has a false
> status that the tests fail, despite the version being tested only now
> existing in stable.
>
> http://ci.debian.net/packages/l/lava-dispatcher/unstable/amd64/
>
> This package is marked as failing despite not testing the version which
> was uploaded on 8th May and which migrated into stretch on 14th May.
>
> http://ci.debian.net/packages/l/lava-tool/unstable/amd64/
>
> Should be testing 0.12-1
>
> Yet some other packages uploaded at the same time have been tested.
>
> http://ci.debian.net/packages/l/lava-coordinator/unstable/amd64/
>
> 0.1.6-2 was tested on 7th May.
>
> http://ci.debian.net/packages/d/django-restricted-resource/unstable/amd64/
> (9th May)
>
> http://ci.debian.net/packages/d/django-testscenarios/unstable/amd64/
> (9th May)
>
> So some tests are being done, just not others.
They all look like timing issues to me, see my response to the first
message of the thread.
--
Antonio Terceiro <terceiro@debian.org>
Attachment:
signature.asc
Description: Digital signature