gh-actions running incorrect tox envs

[adrn]

Relevant parts of my tox.ini look like:

[tox]
envlist =
    py37-cov
    py37-astropy{40,lts}
    py37-devdeps
    py37-numpy{117,118,119}
    py38
    build_docs
    linkcheck

[gh-actions]
python =
    3.7: py37-cov, py37-numpy, py37-astropy, build_docs
    3.8: py38

And I followed the README here to set up my gh actions config file: https://github.com/adrn/pyia/blob/main/.github/workflows/tests.yml

But it looks like the wrong envs are running with versions of Python. For example, in the py3.7 ubuntu test, only py37-cov and build_docs are run. In py3.8 macos, all of the envs are run. https://github.com/adrn/pyia/runs/861918140

Do you have any tips?

Thanks!

[ymyzk]

@adrn, thanks for the question. Let me answer the question on Python 3.7 first.

I assume you want to run the following environments on Python 3.7 jobs.

• py37-cov
• py37-numpy117
• py37-numpy118
• py37-numpy119
• py37-astropy40
• py37-astropylts
• build_docs

If you want to achieve this behavior, we need to update the gh-actions section like this.

[gh-actions]
python =
    3.7: py37-cov, py37-numpy{117,118,119}, py37-astropy{40,lts}, build_docs
    3.8: py38

tox-gh-actions find which environments to run based on factors. Factors are an environment name delimited by hyphens. With the previous configuration, tox-gh-actions tries to find a list of environments which has numpy as a factor. But there's no environment having this as a factor. There's an environment which has numpy117, numpy118, or numpy119 though.

[adrn]

Ah, that makes sense - thanks for the response!

[ymyzk]

I'm still investigating the second issue, Python 3.8 on macOS. As far as I checked logs using tox -vv, it seems tox-gh-actions is not loaded as a tox plugin for some reason. I'm trying to identify the cause.

[ymyzk]

A working example (Python 3.7 + macOS): https://github.com/ymyzk/pyia/runs/865503679

2020-07-13T14:15:50.0641210Z ##[group]Run tox -vv
2020-07-13T14:15:50.0641440Z �[36;1mtox -vv�[0m
2020-07-13T14:15:50.0797190Z shell: /bin/bash -e {0}
2020-07-13T14:15:50.0797330Z env:
2020-07-13T14:15:50.0797540Z   pythonLocation: /Users/runner/hostedtoolcache/Python/3.7.8/x64
2020-07-13T14:15:50.0797660Z ##[endgroup]
2020-07-13T14:15:50.4605150Z using tox.ini: /Users/runner/work/pyia/pyia/tox.ini (pid 1403)
2020-07-13T14:15:50.4829670Z original envconfigs: ['.package', 'py37-cov', 'py38', 'build_docs', 'linkcheck', 'codestyle']
2020-07-13T14:15:50.4830710Z original envlist: ['py37-cov', 'py38', 'build_docs', 'linkcheck']
2020-07-13T14:15:50.4831610Z original envlist_default: ['py37-cov', 'py38', 'build_docs', 'linkcheck']
2020-07-13T14:15:50.4832240Z Python version: 3.7
2020-07-13T14:15:50.4833250Z tox-gh-actions config: {'python': {'3.7': ['py37-cov', 'py37-numpy', 'py37-astropy', 'build_docs'], '3.8': ['py38']}, 'env': {}}
2020-07-13T14:15:50.4834100Z new envlist: ['py37-cov', 'build_docs']
2020-07-13T14:15:50.4931800Z using tox-3.16.1 from /Users/runner/hostedtoolcache/Python/3.7.8/x64/lib/python3.7/site-packages/tox/__init__.py (pid 1403)

A non-working example (Python 3.8 + macOS): https://github.com/ymyzk/pyia/runs/865503728

2020-07-13T14:15:51.7268250Z ##[group]Run tox -vv
2020-07-13T14:15:51.7268490Z �[36;1mtox -vv�[0m
2020-07-13T14:15:51.7413360Z shell: /bin/bash -e {0}
2020-07-13T14:15:51.7413480Z env:
2020-07-13T14:15:51.7413600Z   pythonLocation: /Users/runner/hostedtoolcache/Python/3.8.3/x64
2020-07-13T14:15:51.7413700Z ##[endgroup]
2020-07-13T14:15:52.0636380Z using tox.ini: /Users/runner/work/pyia/pyia/tox.ini (pid 1364)
2020-07-13T14:15:52.0785250Z could not satisfy requires MissingDependency(<Requirement('pip>=19.3.1')>)
2020-07-13T14:15:52.2315380Z using tox-3.16.1 from /Users/runner/hostedtoolcache/Python/3.8.3/x64/lib/python3.8/site-packages/tox/__init__.py (pid 1364)

This part could not satisfy requires MissingDependency(<Requirement('pip>=19.3.1')>) looked suspicious to me. I tried removing the like pip >= 19.3.1 from tox.ini and tox-gh-actions worked (https://github.com/ymyzk/pyia/runs/865542130)

I'm still not clear why adding pip >= 19.3.1 can cause the issue but this seems to be outside of the scope of tox-gh-actions itself. It's likely there's a problem in either tox, tox.ini, or the environment. I can investigate a bit more but I cannot guarantee the response.

[adrn]

Thanks @ymyzk -- this was very helpful!