Jim Brännlund

So I went through the history, specifically [this PR](https://github.com/pytest-dev/pytest-html/pull/270) (and [this one](https://github.com/pytest-dev/pytest-html/pull/420)), and the intention (which the contributor actually noted) was never for the title to be anything other than...

> > In the meantime my suggestion is to use the [`summary (prefix) hook`](https://pytest-html.readthedocs.io/en/latest/user_guide.html#additional-summary-information) to achieve what you're looking for. > > what i see in your link is: >...

> yes, I have seen but what I need to do to avoid the warning? stop using it too? or i can use another module on its place you see...

1. I can’t repro this. Can you provide how to repro? 2. The ini-config or query param?

> 1. no sorry, I was wrong, I was looking at the old report 2. ini config render_collapsed = True i have not understood where to put query param frankly...

Is it just the summary or are they missing in the table (as rows) as well? If pytest reports it, so should the html report

Not sure how active @gnikonorov is these days. According to GitHub is last activity was in Jan 202**2**. I'm happy to pick this up, given the maintainers are willing to...

I just noticed this issue. Not sure if it is an issue, but it is at least unexpected behaviour. I maintain `pytest-html` and whilst a "teardown" is executed - it's...

I'll welcome a PR that supports that!

Changing the example code to fail in the teardown instead: ```python import pytest @pytest.fixture def fix(): assert True yield print("\nTEARDOWN CALLED") assert False @pytest.mark.flaky(reruns=1) def test_logreport(fix): assert True ``` yields...