Closed tolomea closed 1 year ago
Hello @tolomea, thanks for reporting the issue. It seems somethings is working unexpectedly inside tox-gh-actions when we run tox using tox -p
. I'll look deeper and make a bug fix release later.
I'm coming back to a project I haven't touched for 7 months.
The upgrade from tox v3 to v4 and tox-gh-actions v2 to v3 happened during this period is also a contributing factor to this bug.
Meanwhile, could you try using tox p
instead to run your tests in parallel? It seems we can avoid the bug in this way.
I changed it to just "tox" and that fixed it, although I guess slower now
I believe tox p
or tox run-parallel
can run tests in parallel and it won't trigger the bug reported in this thread.
I just released tox-gh-actions v3.1.0 which includes a fix for this issue (#145)
Describe the bug I'm coming back to a project I haven't touched for 7 months. It follows the examples fairly closely. All the CI is broken with the following.
That particular one came off py3.10 with the following:
Any pointers on what to check?