[Qa-jenkins-dev] dpkg, apt and dose3 do not agree in many synthetic dependency situations involving multiarch

[Holger Levsen]

Hi josch,

On Wed, Aug 17, 2016 at 06:25:57AM +0200, Johannes Schauer wrote:
> I want to submit a new jenkins job (patch attached) which implements a check
> whether dpkg, apt and dose3 agree on how to resolve dependencies involving
> multiarch. Below mail describes my original implementation from last year.
> Essentially, the test creates all possible combinations of how two packages can
> relate to each other and then throws the situation at dpkg, apt and dose3
> respectively and checks whether the packages can be installed together or not.
> Since our dependency system is complex, it is possible to come up with 8624
> ways how two packages can relate to each other. Since my message last year, I
> did a complete rewrite of the script and it now also supports source package
> dependencies.

cool!
 
> Please adjust the trigger time for this job as appropriate. I think running
> this once per week would be sufficient.

I guess it's fine…

> Maprepi already pointed out that the name is bad. I don't mind any renaming. I
> just lack creativity to come up with a good name.

I agree the name is bad, because deb-m-a-dep-check doesn't explain
anything and doesn't hint at what you have described in the first
paragraph above.

So I would like dpkg+apt+dos3+depends-consens better as a job name, for
example.

And then I wonder, for which package(s) this job does this or these
tests? for all? Then the job name should probably be
dpkg+apt+dos3+depends-consens-sid or such. Ah, you have that ;)

Also, please reflect what the job does in 
description: 'Build the master branch of https://gitlab.mister-muffin.de/josch/deb-m-a-dep-check'

Last and probably *not* least, I dislike that the actual test code is
living on another server, I would much prefer to run code from stable or
at least sid or from jenkins.d.n.git - but then we have other jobs like
this already…

Do you plan to upload deb-m-a-dep-check to sid anytime soon? (Or why is
it a Debian package? (Which I conclude from the shell command to be run,
I havent actually looked at the git repo ;)

> > Running it takes about 40 minutes and currently requires that you are on amd64

is it single-threaded or will it benefit from multiple cores?

> > Here are some more statistics of the results:
> > 
> > Dpkg and apt agree but dose3 does not: 18.1%
> > Dpkg and dose3 agree but apt does not: 4.7%
> > Apt and dose3 agree but dpkg does not: 20.7%

does that mean, for <60% apt+dpkg+dose3 agree? :-)

> +    name: 'deb-m-a-dep-check_sid'

I think there should be a job run for stretch too, with the same
frequency and probably a monthly run job for jessie as well.

Thanks!


-- 
cheers,
	Holger
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 811 bytes
Desc: Digital signature
URL: <http://lists.alioth.debian.org/pipermail/qa-jenkins-dev/attachments/20160819/a216446c/attachment.sig>