runs autopkgtests on architectures where the package under test does not exist
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| britney |
New
|
Undecided
|
Unassigned | ||
Bug Description
autopkgtests triggered by a new version of the package under test (not a dependency) appear to run on all architectures, even if the package under test has no binaries there.
Such tests are likely to fail even when there is nothing wrong with the package: if they explicitly depend on their own binary they fail to install, while if their dependency is '@' = "all binaries this package builds on this architecture, even if that's nothing", they try to run, and fail because they can't find the program/module being tested.
This usually produces a mostly harmless 'always failed' result. However, when changes in e.g. the allowed Restrictions take such a package from 'all skipped' to 'some tried and failed', this can count as a regression and trap a package in -proposed, e.g. http://
| Matthias Klose (doko) wrote | #1 |
also when the package only has some binaries on that architectures. picard-tools/i386 now triggered by openjdk-* fails on i386, but the packages are now built on amd64 only, the -doc package being the only architecture independent package.