Notes about issue blacklisted_on_jenkins_armhf_only in unstable
Identifier: | blacklisted_on_jenkins_armhf_only |
---|---|
Suites: | unstable / trixie / bookworm / bullseye / experimental |
Description: |
Some packages have been blacklisted only on armhf in our test infrastructure because their builds take too long on the tiny armhf boards we're using. The mitigation against this is to add more architectures or to wait until we test against the debian archive, when it will become sensible to raise the 18h timeout for a single build. Until his happens, please rely on the amd64, i386 and arm64 tests. |
Packages in 'unstable' known to be affected by this issue: (the 1/4 most-popular ones (within this issue) are underlined) |
23 reproducible packages in unstable/amd64:
1 FTBFS packages in unstable/amd64:
9 unreproducible packages in unstable/amd64:
1 404 packages in unstable/amd64:
2 build timeout packages in unstable/amd64:
1 depwait packages in unstable/amd64:
2 blacklisted packages in unstable/amd64:
|
Our notes about issues affecting packages are stored in notes.git and are targeted at packages in Debian in 'unstable/amd64' (unless they say otherwise). |
A package name displayed with a bold
font is an indication that this package has a note. Visited
packages are linked in green, those which have not been visited are
linked in blue.
A #
sign after the name of a package
indicates that a bug is filed against it. Likewise, a
+
sign indicates there is a
patch available, a P
means a
pending bug while #
indicates a
closed bug. In cases of several bugs, the symbol is repeated.