the image for the autopkg tests has a big python3 stack installed
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Auto Package Testing |
New
|
Low
|
Unassigned | ||
Bug Description
the image for the autopkg tests has a big python3 stack installed, that leads to test errors different to Debian, and is different across architectures (armhf != !armhf). These packages should be removed for autopkg testing.
Seen with python-jsonschema failing it's autopkg tests:
http://
http://
amd64: 2020-01-23 20:45:55 UTC
armhf: 2020-01-23 20:09:14 UTC
The jsonschema/
https:/
On non armhf archs, the python3-
This makes it very hard to debug the tests, when you have undocumented packages installed, which are also different across architectures.
As a first step, please list the installed packages in the autopkg tests.
Second, please remove the dependencies installed by cloud-init before running the tests. having a big python3 stack installed by default doesn't help.
| Iain Lane (laney) wrote | #1 |
| Steve Langasek (vorlon) wrote | #2 |
| Changed in auto-package-testing: | |
| importance: | Undecided → Low |
> As a first step, please list the installed packages in the autopkg tests.
In the artifacts, there is a file which lists the packages in the testbed (before your test ran). In the test log itself, you can see which packages the test caused to be installed. So I believe this point is already solved?