| 2023-01-25 14:18:17 |
Paride Legovini |
bug |
|
|
added bug |
| 2023-01-25 14:18:26 |
Paride Legovini |
tags |
|
update-excuse |
|
| 2023-01-25 14:18:29 |
Paride Legovini |
breezy (Ubuntu): assignee |
|
Paride Legovini (paride) |
|
| 2023-01-25 14:41:01 |
Paride Legovini |
description |
There are several autopkgtest failures affecting breezy 3.3.2-1 and preventing it from migrating, e.g.
https://autopkgtest.ubuntu.com/results/autopkgtest-lunar/lunar/amd64/b/breezy/20230124_123950_b8982@/log.gz
According to upstream some tests may be flaky. IRC discussion excerpt:
<paride> these errors are suspicious: ModuleNotFoundError: No module named 'breezy.testingplugins'
<jelmer> so there's some tests that populate breezy.testingplugins in sys.modules
<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. |
There are several autopkgtest failures affecting breezy 3.3.2-1 and preventing it from migrating, e.g.
https://autopkgtest.ubuntu.com/results/autopkgtest-lunar/lunar/amd64/b/breezy/20230124_123950_b8982@/log.gz
According to upstream some tests may be flaky. IRC discussion excerpt:
<paride> these errors are suspicious: ModuleNotFoundError: No module named 'breezy.testingplugins'
<jelmer> so there's some tests that populate breezy.testingplugins in sys.modules
<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. |
|
| 2023-01-25 21:00:01 |
Paride Legovini |
description |
There are several autopkgtest failures affecting breezy 3.3.2-1 and preventing it from migrating, e.g.
https://autopkgtest.ubuntu.com/results/autopkgtest-lunar/lunar/amd64/b/breezy/20230124_123950_b8982@/log.gz
According to upstream some tests may be flaky. IRC discussion excerpt:
<paride> these errors are suspicious: ModuleNotFoundError: No module named 'breezy.testingplugins'
<jelmer> so there's some tests that populate breezy.testingplugins in sys.modules
<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. |
There are several autopkgtest failures affecting breezy 3.3.2-1 and preventing it from migrating, e.g.
https://autopkgtest.ubuntu.com/results/autopkgtest-lunar/lunar/amd64/b/breezy/20230124_123950_b8982@/log.gz
According to upstream some tests may be flaky. IRC discussion excerpt:
<paride> these errors are suspicious: ModuleNotFoundError: No module named 'breezy.testingplugins'
<jelmer> so there's some tests that populate breezy.testingplugins in sys.modules
<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-system-specific
<jelmer> I've never seen it happen in Breezy's CI |
|
| 2023-01-26 08:43:51 |
Paride Legovini |
breezy (Ubuntu): status |
New |
Fix Committed |
|
| 2023-01-26 15:31:35 |
Launchpad Janitor |
breezy (Ubuntu): status |
Fix Committed |
Fix Released |
|
