Skip to content

Skip saltext-zabbix editable-install tests on Python 3.10 - #341

Merged
dwoz merged 2 commits into
mainfrom
fix/skip-saltext-zabbix-py310
Nov 2, 2026
Merged

dwoz merged 2 commits into
mainfrom
fix/skip-saltext-zabbix-py310

Conversation

@dwoz

@dwoz dwoz commented Nov 1, 2026

Copy link
Copy Markdown
Contributor

Summary

  • `tests/test_verify_build.py::test_install_editable_package` and `test_install_editable_package_in_extras` clone HEAD of `salt-extensions/saltext-zabbix` and run `pip install -e saltext-zabbix`.
  • `saltext-zabbix` bumped its `python_requires` to `>=3.11`, so on Python 3.10 pip refuses the install (`ERROR: Package 'saltext-zabbix' requires a different Python: 3.10.22 not in '>=3.11'`) and both tests fail with `AssertionError: assert 1 == 0`.
  • Mark both tests `skipif(sys.version_info < (3, 11))`. They cover the editable-install path, not anything zabbix-specific; the salt-extensions ecosystem is dropping 3.10 broadly so pinning a legacy tag would just defer this. 3.11+ Linux coverage is preserved.

Observed in https://github.com/saltstack/relenv/actions/runs/41045572338 (`Verify Linux (3.10, x86_64)` and `Verify Linux (3.10, aarch64)`), both blocking PR #338.

Test plan

  • CI: `Verify Linux (3.10, x86_64)` and `Verify Linux (3.10, aarch64)` turn green (the two tests show as SKIPPED)
  • CI: `Verify Linux (3.11-3.14, x86_64/aarch64)` stay green (regression — the tests still run on these)

dwoz added 2 commits November 1, 2026 00:38
test_install_editable_package and test_install_editable_package_in_extras
clone HEAD of https://github.com/salt-extensions/saltext-zabbix and run
`pip install -e saltext-zabbix`. saltext-zabbix bumped its python_requires
to >=3.11, so on Python 3.10 pip refuses the install and the tests fail
with ``assert p.returncode == 0``.

Mark both tests skipif(sys.version_info < (3, 11)). They cover the
editable-install path, not anything zabbix-specific, and the salt-extensions
ecosystem is dropping 3.10 broadly, so pinning a legacy tag would just defer
this. Linux 3.11+ coverage is preserved.
The previous commit used ``@pytest.mark.skipif(sys.version_info < (3, 11))``,
which evaluates against the Python running pytest -- the host runner Python
(3.11+), not the relenv-built Python under test. So on the ``Verify Linux
(3.10, ...)`` jobs the marker never fired and the tests still ran against a
3.10 relenv build, hitting the same ``pip install -e saltext-zabbix`` failure.

Move the check inside the test body and gate on the ``minor_version``
fixture (which yields the build Python's ``MAJOR.MINOR``). Matches the
in-body ``pytest.skip(reason=...)`` pattern already used elsewhere in this
file.
@dwoz
dwoz merged commit 8f6d000 into main Nov 2, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant