Seehttps://github.com/jayaddison/html5lib-python/runs/1677406878 for example GitHub Actions build output corresponding toc217133.

GitHub Actions provides 20 parallel workers, have you considered using a matrix to test each Python version in its own worker rather than all in parallel in a single worker? Should be much quicker.

But otherwise, big 👍 for moving from Travis CI to GHA.

@hugovk Thanks! Using a matrix strategy would seem ideal - the challenge is thecombinatorialtoxenvlist, since the Python interpreter versions provided in GitHub Actions don't correspond to thetox.ini-defined interpreter names.

Thetox-gh-actions plugin is fairly widely adopted to solve more-or-less this problem, and it does that by reading a Python-version-to-environment mapping from thetox.ini file (example).

It's worth pausing and thinking about this change for a little while before merge, I think. There may be a way to achieve the worker-per-environment goal in a different way - or perhaps it should be reported / discussed upstream.

tox-dev/tox#659 may be a relevant issue to track relating to this

The latest commits re-attempt a matrix build strategy via GitHub Actions; thegenericpy prefix fortox generative names should map to the 'current default Python interpreter', so the generative factor is removed fromtox.ini and replaced by the GHA YAML configuration.

This does have an unfortunate side-effect that it'll be trickier for developers with a local checkout of the repository to test the package against all Python versions by simply runningtox. Instead it will test against their default Python interpreter. That doesn't seem perfect.

GitHub Actions provides 20 parallel workers, have you considered using a matrix to test each Python version in its own worker rather than all in parallel in a single worker? Should be much quicker.

Ok, my mistake previously@hugovk; I overcomplicated things. Thisdoes look feasible after all, with one caveat/tradeoff regarding developer experience for local checkouts.

Seehttps://github.com/jayaddison/html5lib-python/runs/1691598506 for an example multi-pipeline build via GHA using a matrix strategy

... and perhaps that local checkout dev experience issue is now resolved too. Each GHA worker now runstox -e py, invoking the test suite for a single Python interpreter, as configured via the matrix worker environment list.

The remaining tradeoff/downside is that the environment list now exists intox.ini (for local workflows) and is duplicated in the GHA YAML file.

https://github.com/jayaddison/html5lib-python/actions/runs/481474149 contains the latest build output as per commit19cf7f7

Ping@gsnedders@jgraham@willkg