Hi Otto, On 05-06-2019 15:07, Otto Kekäläinen wrote: >>> https://ci.debian.net/packages/m/mariadb-10.3/unstable/amd64/ >>> perl/5.30.0-1 bubblewrap/0.3.3-1 cpulimit/2.6-1 >>> libmodule-corelist-perl/5.20190522-1 libwebsockets/2.4.2-1 >>> silkaj/0.6.5-2 stunnel4/3:5.54~b3-1 systemd/242-1 >> >> "perl/5.30.0-1" -> this seems to be one of the experiments which >> started recently to run autopkgtests against selected packages from >> experimental. Which can't work for perl 5.30 and is a tad confusing >> as the failures show up under the unstable tests. gregor already pointed in the correct direction here. Yes, these tests are against experimental packages. >> I guess Paul can explain better what's going on on the ci.d.n side. [Added d-ci@l.d.o as CC; I suggest using this as point of contact in the future]. I have started testing packages from experimental in unstable in the same way as we do for unstable to testing. This is meant to be a service to the maintainers in the near future, especially during periods of freeze. Expect an announcement to d-d-a soonish. > Thanks for the info! > > It also shows up at https://tracker.debian.org/pkg/mariadb-10.3 > indicating it is something the package maintainer needs to address.. > But now I know there is nothing to do about it now. Yes, currently the export of ci.d.n towards external consumers is lagging behind the use of ci.d.n. I hope that our current Outreachy project will improve this. The main problem is that in our json with results, the latest result is reported, regardless of the combination of pinned packages. In the future this json should only report "pure" suite results. Paul
Attachment:
signature.asc
Description: OpenPGP digital signature