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

Bug#978750: openjdk-N (non-default) should not trigger autopkg tests



Control: retitle -1 britney: autopkgtest only tests first alternative

Hi,

On 31-12-2020 10:55, Matthias Klose wrote:
> openjdk-N (non-default) should not trigger autopkg tests. 

Maybe, but default-jre, openjdk-11-jre, openjdk-13-jre, openjdk-14-jre,
openjdk-15-jre, openjdk-16-jre, openjdk-8-jre all provide e.g.
java5-runtime, so if a package depends on it, there's a relation to
could be tested. However, there's nothing in place to force the test to
run with an non-default alternative, so scheduling a test currently
doesn't make much sense.

> All these don't make
> any sense, as the tests are always run using the default JRE/JDK.

I agree that the current situation doesn't really enforce to test the
right thing yet, but if we think it's worth while, we could work on
fixing that.

> E.g. for 13, these were triggered today:

[...]
> autopkgtest for android-platform-tools-apksig: amd64: Test in progress, arm64:
> Test in progress, armhf: Test in progress, i386: Test in progress, ppc64el: Test
> in progress

apksigner depends: default-jre | java8-runtime | java9-runtime |
java10-runtime | java11-runtime

Paul

Attachment: OpenPGP_signature
Description: OpenPGP digital signature


Reply to: