Description
The check-release-notes job in the CI: Release workflow (release.yml) fails at the "Self-test release-notes checker" step with pytest exit code 4 (collection error).
Example failure: https://github.com/NVIDIA/cuda-python/actions/runs/25701496246/job/75462415468
Root cause
The step runs:
- name: Self-test release-notes checker
run: |
pip install pytest
pytest ci/tools/testsWhen pytest launches from the repo root, it discovers the root-level conftest.py, which imports cuda.pathfinder. Since the job only installs pytest (not the project packages), the import fails and pytest aborts before any tests run.
The actual release-notes file (cuda_core/docs/source/release/1.0.0-notes.rst) is fine — the job never reaches the "Check versioned release notes exist" step.
Suggested fix
Remove the self-test step from the release workflow entirely. Running infra/tooling tests during a release is not the right place — they should be validated separately (e.g. in a CI workflow that runs on PRs).
For reference, this was already worked around by commenting out the step in a release branch: 40508c5
Description
The
check-release-notesjob in theCI: Releaseworkflow (release.yml) fails at the "Self-test release-notes checker" step with pytest exit code 4 (collection error).Example failure: https://github.com/NVIDIA/cuda-python/actions/runs/25701496246/job/75462415468
Root cause
The step runs:
When pytest launches from the repo root, it discovers the root-level
conftest.py, which importscuda.pathfinder. Since the job only installspytest(not the project packages), the import fails and pytest aborts before any tests run.The actual release-notes file (
cuda_core/docs/source/release/1.0.0-notes.rst) is fine — the job never reaches the "Check versioned release notes exist" step.Suggested fix
Remove the self-test step from the release workflow entirely. Running infra/tooling tests during a release is not the right place — they should be validated separately (e.g. in a CI workflow that runs on PRs).
For reference, this was already worked around by commenting out the step in a release branch: 40508c5