python-pytest-lazy-fixture: autopkgtest regression with pytest 8
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
pycoast (Ubuntu) |
New
|
Undecided
|
Unassigned | ||
pytest (Ubuntu) |
New
|
Undecided
|
Unassigned | ||
python-pytest-lazy-fixture (Debian) |
Confirmed
|
Unknown
|
|||
python-pytest-lazy-fixture (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
Imported from Debian bug http://
Package: python-
Version: 0.6.3-2
Severity: important
User: <email address hidden>
Usertags: pytest-8
Dear maintainer,
your package has a autopkgtest regression with pytest 8.
Typically, packages will start failing if they
- have deprecation warnings of type PytestRemovedIn
- assume a particular pytest stdout/stderr output which might have
changed, or
- rely on implementation details of the pytest test collector, in
particular the pytest.Package class, which has been redesigned for
pytest 8.
Please refer to the upstream changelog [1] for a complete list of
breaking changes and the pytest (pseudo-)excuses [2] related to your
package for details of the regression.
It is possible that the autopkgtest regression is not directly caused
by python-
that case, feel free to reassign the bug and mark your package as
affected, but do not close the bug until the autopkgtest passes.
Cheers Timo
[1]
https:/
12-30 [2]
https:/
tags: | added: update-excuse |
Changed in python-pytest-lazy-fixture (Debian): | |
importance: | Undecided → Unknown |
status: | New → Confirmed |