| Version annotated: |
20160125-1 |
|
Identified issues:
|
|
Identifier:
|
blacklisted_on_jenkins
|
|
Description
|
Some packages have been blacklisted in our test infrastructure because
their build hangs, takes too long, spawns processes that are not killed, or
simply because they use too many resources for our current capacity. (This
is purely practical step - we would like to test these packages.)
|
|
Identifier:
|
blacklisted_on_jenkins_armhf_only
|
|
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.
|
|
|
Comments:
|
Blacklisted because this package just FTBFSes most of the time. It's only
used by the GCC maintainer to experiment and test new releases before
updating the gcc-X packages, so no big deal.
|
| |
|
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).
|