Bug#1073443: pytest-rerunfailures: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p "3.12 3.11" returned exit code 13

[Timo Röhling]

Control: forwarded 1073443 https://github.com/pytest-dev/pytest/issues/12284
Control: tags 1073443 + upstream

It looks like rerunfailures plugin erroneously deletes the session
teardown from the execution stack if a test fails and is rerun. You
can reproduce the bug with the attached script
pytest_session_fixture.py:

- Running `pytest pytest_session_fixture.py -s` will show "session teardown"
is run regardless of the flaky test outcome
- Running `pytest pytest_session_fixture.py -s --reruns 1` will only show
"session teardown" if the flaky test succeeds on the first try.

This bug was exposed by a change in pytest 8.2 and currently
prevents pytest from migrating to testing.


Cheers
Timo

[Debian Bug Tracking System]

Post by Timo Röhling
forwarded 1073443 https://github.com/pytest-dev/pytest/issues/12284

Bug #1073443 [src:pytest-rerunfailures] pytest-rerunfailures: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p "3.12 3.11" returned exit code 13
Set Bug forwarded-to-address to 'https://github.com/pytest-dev/pytest/issues/12284'.

Post by Timo Röhling
tags 1073443 + upstream

Bug #1073443 [src:pytest-rerunfailures] pytest-rerunfailures: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p "3.12 3.11" returned exit code 13
Added tag(s) upstream.

[Debian Bug Tracking System]

tags -1 ftbfs

Bug #1073443 [src:pytest-rerunfailures] pytest-rerunfailures: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p "3.12 3.11" returned exit code 13
Ignoring request to alter tags of bug #1073443 to the same tags previously set

[Bastian Venthur]

Source: pytest-rerunfailures
Version: 12.0-1
Followup-For: Bug #1073443
X-Debbugs-Cc: ***@debian.org
Control: tags -1 ftbfs

Hi,

apparently, this bug will cause a lot of packages to be removed from testing
due to the transitive reverse dependencies[1]. Is there any update on this bug?
Or any workaround for the packages that are about to be removed from testing
soon?


Cheers,

Bastian

[1] https://tracker.debian.org/pkg/pytest-rerunfailures

-- System Information:
Debian Release: trixie/sid
APT prefers unstable
APT policy: (500, 'unstable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 6.11.4-amd64 (SMP w/16 CPU threads; PREEMPT)
Kernel taint flags: TAINT_WARN
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

[Debian Bug Tracking System]

tag -1 pending

Bug #1073443 [src:pytest-rerunfailures] pytest-rerunfailures: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p "3.12 3.11" returned exit code 13
Added tag(s) pending.

[Jochen Sprickerhof]

Control: tag -1 pending

Hello,

Bug #1073443 in pytest-rerunfailures reported by you has been fixed in the
Git repository and is awaiting an upload. You can see the commit
message below and you can check the diff of the fix at:

https://salsa.debian.org/python-team/packages/pytest-rerunfailures/-/commit/a5597e0da12b4a3484fc6a132309a166361bcf6e

------------------------------------------------------------------------
fix compatibility with pytest 8.2

Closes: #1073443
------------------------------------------------------------------------

(this message was generated automatically)

[Debian Bug Tracking System]

Your message dated Tue, 05 Nov 2024 16:20:04 +0000
with message-id <E1t8MHk-007P5h-***@fasolo.debian.org>
and subject line Bug#1073443: fixed in pytest-rerunfailures 14.0-2
has caused the Debian Bug report #1073443,
regarding pytest-rerunfailures: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p "3.12 3.11" returned exit code 13
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ***@bugs.debian.org
immediately.)