Custom install_command is not run on GitHub Actions

[tbrlpld]

Describe the bug

The custom install_command from tox.ini seems to be ignored.

If my command depends on packages that should be installed with the install_command I get errors when running on GitHub Actions, but not locally.

To Reproduce

• GitHub Actions configuration

name: Laces CI

on:
  push:
    branches:
      - main
      - 'stable/**'

  pull_request:

concurrency:
  group: ${{ github.workflow }}-${{ github.ref }}
  cancel-in-progress: true

permissions:
  contents: read # to fetch code (actions/checkout)

jobs:
  lint:
    runs-on: ubuntu-latest
    steps:
      - uses: actions/checkout@v3
        with:
          fetch-depth: 0
      - name: Set up Python 3.8
        uses: actions/setup-python@v4
        with:
          python-version: '3.8'
      - uses: pre-commit/action@v3.0.0

  test-sqlite:
    runs-on: ubuntu-latest
    needs: lint
    strategy:
      matrix:
        python: ['3.8', '3.9', '3.10', '3.11']

    steps:
      - uses: actions/checkout@v3
      - name: Set up Python ${{ matrix.python }}
        uses: actions/setup-python@v4
        with:
          python-version: ${{ matrix.python }}
      - name: Install
        run: |
          python -m pip install --upgrade pip setuptools wheel
          python -m pip install .[ci]
      - name: Test
        run: tox -vv
        env:
          DB: sqlite
      - name: Upload coverage reports to Codecov
        uses: codecov/codecov-action@v3
        env:
          CODECOV_TOKEN: ${{ secrets.CODECOV_TOKEN }}
        with:
          files: ./.coverage.json

• tox and tox-gh-actions configuration

[tox]
skipsdist = True
usedevelop = True

envlist =
    python{3.8,3.9,3.10,3.11}-django{3.2,4.1,4.2}


[gh-actions]
python =
    3.8: python3.8
    3.9: python3.9
    3.10: python3.10
    3.11: python3.11

[gh-actions:env]
DB =
    sqlite: sqlite

[testenv]
install_command = python -m pip install -e ".[testing]" -U {opts} {packages}

commands_pre =
    # Mostly to check that the requirements are in order
    python -m pip freeze

commands =
    coverage run -a testmanage.py test --deprecation all {posargs: -v 2}

commands_post =
    coverage json --data-file .coverage -o .coverage.json

basepython =
    python3.8: python3.8
    python3.9: python3.9
    python3.10: python3.10
    python3.11: python3.11

deps =
    django3.2: Django>=3.2,<4.0
    django4.0: Django>=4.0,<4.1
    django4.1: Django>=4.1,<4.2
    django4.2: Django>=4.2,<4.3
    djangomain: git+https://github.com/django/django.git@main#egg=Django

[testenv:interactive]
basepython = python3.10

commands_pre =
    python {toxinidir}/testmanage.py makemigrations
    python {toxinidir}/testmanage.py migrate
    python {toxinidir}/testmanage.py shell -c "from django.contrib.auth.models import User;(not User.objects.filter(username='admin').exists()) and User.objects.create_superuser('admin', 'super@example.com', 'changeme')"
    python {toxinidir}/testmanage.py createcachetable

commands =
    {posargs:python testmanage.py runserver 0.0.0.0:8020}

setenv =
    INTERACTIVE = 1

• Link to the GitHub Actions job if a repository is public:
  • Here is a run that failed: https://github.com/tbrlpld/laces/actions/runs/7604822530/job/20708230969#step:5:113
  • The failing dependency is coverage.
  • I can also not see any logging of the install step, which makes this hard to debug. I am already running with tox -vv.

Expected behavior

The custom install command should be used to install the dependencies.

Additional context

• tox: 4.11.3
• tox-gh-actions: 3.13

[ymyzk]

Hello, @tbrlpld.

Looking at your GitHub Actions execution log, it seems the py environment is running which is probably what you don't expect. https://github.com/tbrlpld/laces/actions/runs/7604822530/job/20708230969#step:5:110 I guess you expect to run python3.10-django{3.2,4.1,4.2} on Python 3.10.

I think the following part in your configuration is unnecessary, unless you want to use the DB environment variable to decide which tox envs to run. Please see README for more details on when to use the env section.

[gh-actions:env]
DB =
    sqlite: sqlite

[tbrlpld]

Thanks @ymyzk . I'll give that a go.

I did derive this action from one that supported multiple databases. So yea, I guess this is not needed.

[tbrlpld]

@ymyzk Thanks so much! That was in fact the issue. It also solved the issue that the other Django variants were previously not tested in CI. 👍 Amazing fix.