forked from PyCQA/pylint-pytest
-
Notifications
You must be signed in to change notification settings - Fork 3
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Why does tox in Github Actions on Pull Request pull ALL the Pythons (**INCLUDING** 3.12)? #16
Comments
... ofc, the easy way would be to just not have a |
stdedos
added a commit
to stdedos/pylint-pytest
that referenced
this issue
Oct 18, 2023
* Drop `py312` to combat pylint-dev#16 * Install editable, so that python uses the correct source files * Ignore `tests/input/**/*.py` from coverage - they are not ran properly * Again improve on artifact naming Signed-off-by: Stavros Ntentos <133706+stdedos@users.noreply.github.com>
Merged
stdedos
added a commit
to stdedos/pylint-pytest
that referenced
this issue
Oct 18, 2023
* Drop `py312` to combat pylint-dev#16 * Install editable, so that python uses the correct source files * Ignore `tests/input/**/*.py` from coverage - they are not ran properly * Again improve on artifact naming Signed-off-by: Stavros Ntentos <133706+stdedos@users.noreply.github.com>
stdedos
added a commit
to stdedos/pylint-pytest
that referenced
this issue
Oct 18, 2023
* Drop `py312` to combat pylint-dev#16 * Install `--editable`, so that python uses the correct source files * Ignore `tests/input/**/*.py` from coverage - they are not ran properly * Again improve on artifact naming Signed-off-by: Stavros Ntentos <133706+stdedos@users.noreply.github.com>
stdedos
added a commit
to stdedos/pylint-pytest
that referenced
this issue
Oct 18, 2023
* Drop `py312` to combat pylint-dev#16 * Install `--editable`, so that Python uses the correct source files * Ignore `tests/input/**/*.py` from coverage - they are not ran properly * Again improve on artifact naming Signed-off-by: Stavros Ntentos <133706+stdedos@users.noreply.github.com>
stdedos
added a commit
to stdedos/pylint-pytest
that referenced
this issue
Oct 18, 2023
* Drop `py312` to combat pylint-dev#16 * Install `--editable`, so that Python uses the correct source files * Ignore `tests/input/**/*.py` from coverage - they are not ran properly * Again improve on artifact naming Signed-off-by: Stavros Ntentos <133706+stdedos@users.noreply.github.com>
stdedos
added a commit
to stdedos/pylint-pytest
that referenced
this issue
Oct 18, 2023
* Drop `py312` to combat pylint-dev#16 * Install `--editable`, so that Python uses the correct source files * Ignore `tests/input/**/*.py` from coverage - they are not ran properly * Again improve on artifact naming Signed-off-by: Stavros Ntentos <133706+stdedos@users.noreply.github.com>
stdedos
added a commit
to stdedos/pylint-pytest
that referenced
this issue
Oct 18, 2023
* Drop `py312` to combat pylint-dev#16 * Install `--editable`, so that Python uses the correct source files for coverage * Ignore `tests/input/**/*.py` from coverage - they are not ran properly * Again improve on artifact naming Signed-off-by: Stavros Ntentos <133706+stdedos@users.noreply.github.com>
stdedos
added a commit
that referenced
this issue
Dec 4, 2023
Signed-off-by: Stavros Ntentos <133706+stdedos@users.noreply.github.com>
Internal GH stuff. We cannot do anything about it; issue comes from upstream. Resolution: Just ignore it and run for all found Pythons; but ignore missing envs (c5af2e5). |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
https://github.com/pylint-dev/pylint-pytest/actions/runs/6557075634/job/17831455987?pr=2
Tracked: https://support.github.com/ticket/personal/0/2385967
The text was updated successfully, but these errors were encountered: