autopkgtest failures with breezy 3.3.2-1
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
breezy (Ubuntu) |
Fix Released
|
Undecided
|
Paride Legovini |
Bug Description
There are several autopkgtest failures affecting breezy 3.3.2-1 and preventing it from migrating, e.g.
According to upstream some tests may be flaky. IRC discussion excerpt:
<paride> these errors are suspicious: ModuleNotFoundE
<jelmer> so there's some tests that populate breezy.
<jelmer> they're also meant to clean up the modifications they do
<jelmer> but for some reason that doesn't happen, and then it bites us later on when we iterate over all the modules
The plan is to disable the flaky modules in Ubuntu. Given that the failure is with the test harness and not with the tests themselves this isn't a blind "let's ignore test failures" move.
This also happens in Debian, but an autopkgtest failure is not blocking there. Again according to upstream:
<jelmer> this particular regression does appear to be Debian-
<jelmer> I've never seen it happen in Breezy's CI
tags: | added: update-excuse |
Changed in breezy (Ubuntu): | |
assignee: | nobody → Paride Legovini (paride) |
description: | updated |
description: | updated |
Changed in breezy (Ubuntu): | |
status: | New → Fix Committed |
I disabled test_plugins by passing -x test_plugins to the command line in debian/ tests/testsuite 3 per upstream suggestion (thanks!) and it passed locally:
OK (known_failures=46) ------- ------- --] @@@@@@@ @@@@@@ summary
4824 tests skipped
autopkgtest [14:16:21]: test testsuite3: -------
autopkgtest [14:16:21]: test testsuite3: - - - - - - - - - - results - - - - - - - - - -
testsuite3 PASS
autopkgtest [14:16:21]: @@@@@@@
testsuite3 PASS