Hi Paul,
On Thu, Apr 02, 2020 at 05:20:54PM +0200, Paul Gevers wrote:
> It depends what you look for. If you're concerned about failures that
> will impact migration, the canonical place is:
> https://release.debian.org/britney/excuses.yaml.gz (or the non-zipped
> version) or directly (around 20 minutes earlier) on respighi. This yaml
> includes the links you are looking for.
I've checked this and found some missings for our purpose. For example
that file contains some instances of deepnano but only as a rdepends of
theano:
$ grep -B11 -A2 deepnano excuses.yaml | grep -v -e ' - null' -e '[wd]-version'
-e '^ m' | sed -e '/^--/,/arm64:/d' -e '/policy_info/,/autopkgtest:/d'
item-name: theano
deepnano:
amd64:
- RUNNING-ALWAYSFAIL
- https://ci.debian.net/status/pending
- https://ci.debian.net/packages/d/deepnano/testing/amd64
arm64:
- RUNNING-ALWAYSFAIL
- https://ci.debian.net/status/pending
- https://ci.debian.net/packages/d/deepnano/testing/arm64
- PASS
-
https://ci.debian.net/data/autopkgtest/testing/arm64/d/debconf-kde/4796849/log.gz
- https://ci.debian.net/packages/d/debconf-kde/testing/arm64
deepnano:
amd64:
- RUNNING-ALWAYSFAIL
- https://ci.debian.net/status/pending
- https://ci.debian.net/packages/d/deepnano/testing/amd64
arm64:
- RUNNING-ALWAYSFAIL
- https://ci.debian.net/status/pending
- https://ci.debian.net/packages/d/deepnano/testing/arm64
- PASS
-
https://ci.debian.net/data/autopkgtest/testing/arm64/d/dask/4786421/log.gz
- https://ci.debian.net/packages/d/dask/testing/arm64
deepnano:
amd64:
- RUNNING-ALWAYSFAIL
- https://ci.debian.net/status/pending
- https://ci.debian.net/packages/d/deepnano/testing/amd64
arm64:
- RUNNING-ALWAYSFAIL
- https://ci.debian.net/status/pending
- https://ci.debian.net/packages/d/deepnano/testing/arm64
Please excuse my rough parsing of that yaml file.
Now since I became suspicious about deepnano itself when checking tracker
https://tracker.debian.org/pkg/deepnano
it does not even have any debci entry despite deepnano has an autopkgtest.
I admit I consider this a bug in tracker.
> If you're more interested in regressions is pure suites (like DDPO is
> showing), than the results are available from
> https://ci.debian.net/data/status/ e.g.
> https://ci.debian.net/data/status/testing/amd64/packages.json for
When greping this file for deepnano I get no hit at all.
> testing/amd64 The URL needs to be constructed:
> https://ci.debian.net/data/autopkgtest/testing/amd64/<package_letter>/<package>/<run_id>/log.gz
> where package_letter is the first character for all packages except
> packages that start with lib, where <package_letter> are the first four
> characters.
Hmmm, it seems I really need to parse these URLs
https://ci.debian.net/packages/d/deepnano/ [1]
for all source packages (in the same way as for deepnano) which seems to
be no straightforward way. I wonder whether you could drop some easily
parsable file containing
source architecture pass version version_that_has_passed_before
or something like this - probably I've missed some important field. This
could be importet into UDD and tracker could base on some UDD table that
imports this information.
Do you think it is feasible to put those data somewhere for easy UDD
import?
OK, when reading [1] it says:
This package is currently blacklisted and will not have any new test runs.
but why? My goal is to assemble information about all Blends packages
featuring an autopkgtest that fails to give people intending to do some
QA work a good place to look for tasks. I have no idea how I can easily
get this information in a structured way.
Kind regards
Andreas.
--
http://fam-tille.de
