Merge ~ubuntu-release/britney/+git/britney2-ubuntu:dropped-tests into ~ubuntu-release/britney/+git/britney2-ubuntu:master
Status: | Merged |
---|---|
Merged at revision: | 41d51369f54d695153fcd71043b511883392a5bf |
Proposed branch: | ~ubuntu-release/britney/+git/britney2-ubuntu:dropped-tests |
Merge into: | ~ubuntu-release/britney/+git/britney2-ubuntu:master |
Diff against target: |
57 lines (+36/-0) 2 files modified
britney2/policies/autopkgtest.py (+5/-0) tests/test_autopkgtest.py (+31/-0) |
Related bugs: |
Reviewer | Review Type | Date Requested | Status |
---|---|---|---|
Andy Whitcroft | Pending | ||
Steve Langasek | Pending | ||
Adam Conrad | Pending | ||
Ubuntu Release Team | Pending | ||
Review via email: mp+314834@code.launchpad.net |
Description of the change
We request tests of packages which have dropped their autopkgtest in unstable. Since we know whether a package has an autopkgtest or not, we can avoid doing this.
Current example is ncbi-tools6 in zesty-proposed.
There's a pass where we directly request tests of the migration item "foo" if it has a test. This bit is okay currently: it will not make a request if foo doesn't have a test in unstable. Then there is a second pass where we trigger test requests for sources which build binaries that depend on foo. I think this is where the problem arises - if foo builds libfoo1 and foo-tools which depends on libfoo1, we trigger a test of foo again even though this is what we are trying to migrate and it no longer has a test.
I think we should ignore foo at this second step - that's what this branch does.