Jim Brännlund

> xref #485. As a PyPy dev, we have dropped support for PyPy3.6, and are going to drop PyPy3.7 soon. > > A known issue is that coverage, which on...

@mattip Seems adding `fetch-depth: 0` to the checkout solved it. 🤷‍♂️ Any idea why the pypy3-tests on mac took almost 30 minutes compared to roughly one minute on regular python?

> No, that is indeed strange. We expect tests to run 2x slower since that is roughly the speed of our interpreter vs. CPython (without the JIT) and tests typically...

> On ubuntu 20.04, when I run with PyPy 3.8 I get 20 seconds, with CPython 3.8 10s. This is the 2x I would expect. Running CPython with coverage does...

> Could I add something like [this](https://github.com/napari/napari/pull/4518) to the test setup to upload `--durations` timings as an artifact, and then compare them via https://carreau.github.io/pytest-json-report-viewer/ ? Absolutely!

> I particular have seen @ssbarnea's work in general and would welcome him as a contributor to pytest-html. If nobody objects I would be happy to send him an invitation...

> Hi there, unfortunately since last year I could not find time to contribute to Pytest-HTML since I have a full time job and this year was not particularly easy...

> One of the first things I want to do is to migrate testing to Github Actions as it far more reliable and flexible than Travis, and assure we have...

> > I haven't experienced any reliability issues with Travis, and I do believe they support scheduled runs - I'm just not sure if they are available on the free/OS...

> > I think more or less all pytest-dev plugins (incl. pytest itself) uses Travis, so I'm against moving to Github Actions unless there's very good reason to do so....