Phantom <lambda> teardown entries with unknown status when using pytest 9.1+ #918

Description

When using allure-pytest (2.15.3 or 2.16.0) with pytest >= 9.1.0, every fixture produces a phantom <fixture>::<lambda> afterStage entry in the Allure report with unknown status. These entries are not real teardown failures — they are internal pytest finalizers that allure wraps but are never invoked through allure's wrapper.

Versions

• pytest: 9.1.1
• allure-pytest: 2.16.0
• Python: 3.12
  Works correctly with pytest <= 9.0.x.