Skip to content

CI: set an explicit python-version for test-crc32c and test-zarr - #856

Open
glaziermag wants to merge 1 commit into
zarr-developers:mainfrom
glaziermag:ci-pin-python-version
Open

CI: set an explicit python-version for test-crc32c and test-zarr#856
glaziermag wants to merge 1 commit into
zarr-developers:mainfrom
glaziermag:ci-pin-python-version

Conversation

@glaziermag

Copy link
Copy Markdown

Sets an explicit python-version: "3.13" on the setup-python steps of the test-crc32c and test-zarr jobs, restoring the interpreter they were pinned to before #839. Since that PR, both jobs pass ${{ matrix.python-version }} to setup-python while neither matrix defines the key, so all six variants have been running on the runner's system Python (3.12.3) — details and log evidence in #855.

Closes #855.

Happy to switch this to a python-version matrix axis instead if version × variant coverage is preferred.

TODO:

  • Unit tests and/or doctests in docstrings — N/A, CI configuration only
  • Tests pass locally — N/A
  • Docstrings and API docs for any new/modified user-facing classes and functions — N/A
  • Changes documented in docs/release.rst — N/A, no library change
  • Docs build locally — N/A
  • GitHub Actions CI passes — awaiting first-contribution run approval
  • Test coverage to 100% (Codecov passes) — unaffected

AI assistance was used; the two-line diff and the affected job logs were re-checked by hand.

Both jobs passed `${{ matrix.python-version }}` to setup-python, but
neither matrix defines that key, so they have run on the runner's system
Python since zarr-developers#839. Pin 3.13, restoring the pre-zarr-developers#839 interpreter.

Closes zarr-developers#855.
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.

CI: test-crc32c and test-zarr run on system Python — matrix.python-version is never defined

1 participant