GV

GeezerVison

The World Wide Web, restored to 800 pixels of glory.

Home|About|Gaming cabinet|Archives|How it works|Starter sites

On this site

  • Sign in
  • ActionsCI/CD and automation
  • CodespacesCloud development environments
  • All Features
  • Documentation
  • Training
  • Certifications
  • Build with Copilot
  • Customize Copilot
  • Integrations
  • Trending repos
  • GitHub Sponsors
  • Developer articles
  • Enterprises

This view

  • Original page
  • New address

GeezerVison is showing github.com — Duplicated test case statuses reported with pytest-rerunfailures, retries section is empty · Issue #735 · allure-framework/allure-python

Duplicated test case statuses reported with pytest-rerunfailures, retries section is empty #735

New issue
Copy link
New issue
Copy link
Closed
#736
Closed
Duplicated test case statuses reported with pytest-rerunfailures, retries section is empty#735
#736
Copy link
Labels
bugSomething isn't workingSomething isn't workingtheme:pytest

Description

@plume-aostrowski
plume-aostrowski
opened on Mar 9, 2023
Issue body actions

I'm submitting a ...

  • bug report
  • feature request
  • support request => Please do not submit support request here, see note at the top of this template.

What is the current behavior?

Tests that are re-run with pytset-rerunfailures are reported as multiple failures, while the "Retries" tab remains empty - as visible on the attached screenshot.
Screenshot from 2023-03-09 14-17-34

If the current behavior is a bug, please provide the steps to reproduce and if possible a minimal demo of the problem

The contents of the test script, in this case test_me_2.py:

def test_fail():
    assert False

Execute pytest --reruns=2 --alluredir=<allure_dir> test_me_2.py
And then display the allure report.

The environment (venv) contents:

allure-pytest==2.13.0
allure-python-commons==2.13.0
attrs==22.2.0
exceptiongroup==1.1.0
iniconfig==2.0.0
packaging==23.0
pluggy==1.0.0
pytest==7.2.2
pytest-rerunfailures==11.1.2
six==1.16.0
tomli==2.0.1

What is the expected behavior?

Tests are reported once, in this case it is obviously a failure by design, the re-runs end up in the "Retries" section as on the screenshot below. This is the report I'm seeing when using allure-pytest-2.12.0:
Screenshot from 2023-03-09 14-19-24

What is the motivation / use case for changing the behavior?

The plugin pytest-rerunfailures is a common pytest plugin to make an attempt at re-running flaky tests. Allure used to work perfectly with it, now it doesn't.

Please tell us about your environment:

  • Allure version: 2.10.0
  • Test framework: [email protected]
  • Allure adaptor: [email protected]

Other information

Activity

  1. delatrie
    added
    bugSomething isn't workingSomething isn't working
    theme:pytest
    on Mar 9, 2023
  2. delatrie commented on Mar 14, 2023

    @delatrie
    delatrie
    on Mar 14, 2023
    Contributor
    More actions

    Hi, @plume-aostrowski! Thanks for the report.
    The fix is on its way!

  3. delatrie
    closed this as completedin #736on Mar 14, 2023
  4. delatrie
    added a commit that references this issue on Mar 14, 2023

    Fix squashed results when using rerunfailures (fixes #735) (#736)

    This issue will close once commit 12085cd is merged into the 'master' branch.
    12085cd
  5. plume-aostrowski commented on Mar 15, 2023

    @plume-aostrowski
    plume-aostrowski
    on Mar 15, 2023
    Author
    More actions

    Thanks for sorting it out so quickly!

  6. beckerGil
    added a commit that references this issue on Apr 10, 2023

    Fix squashed results when using rerunfailures (fixes allure-framework…

    This issue will close once commit 607c23f is merged into the 'master' branch.
    607c23f
  7. IvanBuruyane
    added a commit that references this issue on Mar 19, 2024

    Fix squashed results when using rerunfailures (fixes allure-framework…

    This issue will close once commit a9f6e71 is merged into the 'master' branch.
    a9f6e71
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    bugSomething isn't workingSomething isn't workingtheme:pytest

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions

      You are visitor 01402503 — GeezerVison does not store the pages you look up.
      Best viewed with Netscape Navigator 4.7 or Internet Explorer 6 at 800×600. No cookies required.