[nekdan]

Fixes #918
Supersedes #921

Context

Starting from pytest 9.1.0, FixtureDef.execute() registers an internal lambda finalizer (lambda: request.node.ihook.pytest_fixture_post_finalizer(...)) into fixturedef._finalizers at index 0 before invoking pytest_fixture_setup.

Previously, AllureListener.pytest_fixture_setup wrapped all entries in fixturedef._finalizers with allure_commons.fixture. When pytest ran that internal finalizer at teardown, pytest_fixture_post_finalizer triggered allure_logger.stop_group() and flushed the TestResultContainer to disk before allure_commons.fixture reached stop_after_fixture(), leaving a phantom <fixture>::<lambda> entry with unknown status in every fixture teardown.

Changes

• Record the number of pre-existing internal finalizers on fixturedef._finalizers before yield in AllureListener.pytest_fixture_setup and wrap only user-registered finalizers added during fixture execution.
• Preserve user-defined request.addfinalizer(lambda: ...) reporting (unlike filtering by "<lambda>" name).
• Add acceptance tests verifying both yield fixtures and explicit user lambda finalizers.

Checklist

• Sign Allure CLA
• Provide unit tests

[CLAassistant]

All committers have signed the CLA.