autopkgtest failures in mantic
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
python-mechanicalsoup (Ubuntu) |
Fix Released
|
Undecided
|
Unassigned |
Bug Description
Autopkgtests are failing consistently and persistently for all architectures in mantic for this package.
The error logs show "504 Gateway Time-out" which initially sounded like a flaky test issue that would resolve on retriggering, but ample retriggers have proven that to be not the case.
python-
https:/
Setting up python3-iniconfig (1.1.1-2) ...
Setting up python3-py (1.11.0-1) ...
Setting up python3-all (3.11.2-1) ... ### 3.10.6-1 before
Setting up python3-packaging (23.0-1) ... ### 21.3-1.1 before
Setting up python3-
Setting up python3-pluggy (1.0.0+repack-1) ...
Setting up libxslt1.1:amd64 (1.1.35-1) ...
Setting up python3-soupsieve (2.4.1-2) ... ### 2.3.2-1 before
Setting up python3-pytest (7.2.1-2) ... ### 7.1.2-2ubuntu1 before
Setting up python3-bs4 (4.12.2-2) ... ### 4.11.1-1 before
Setting up python3-pytest-mock (3.8.2-3) ... ### 3.8.2-2 before
Setting up python3-lxml:amd64 (4.9.2-1build1) ... ### 4.9.1-1build1 before
Setting up python3-
Given that the current logs show more test failures than the logs from when it initially failed, I suspect there might be more than one issue at play. But at least a no-change rebuild seems like the first thing to try.
After the no-change rebuild, running against -proposed, the test logs show 6 FAILED tests, versus 14 previously. So, as I expected the rebuild may have helped but there seem to be additional problems.
When I run the no-change rebuild against mantic-release instead, with no triggers except itself, I see only 2 FAILED tests. Running autopkgtest locally in LXC I see these same 2 failures. These seem to be the original "504 Gateway Time-out" and "502 Bad Gateway" errors that I thought might be flaky infrastructure but clearly are not since they repro on my own hw. Debian's CI system appears to show these same two failures in its logs as well.
So, it looks like in addition to whatever the no-change rebuild fixed, there is also this gateway error, plus potentially new issues arising from one or more package updates currently in -proposed.