Redesign PyPy 3.9 CI pipeline: drop dep pins, add step-level failure handling#678
Merged
wbarnha merged 1 commit intoJul 7, 2026
Conversation
Copilot created this pull request from a session on behalf of
wbarnha
July 7, 2026 12:41
View session
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
PyPy 3.9 fails CI both at install time (PyO3 incompatibilities with
cryptography≥45andnh3≥0.3) and at test time (4 persistent failures). The previous fix pinned those deps inrequirements/test.txt, which is the wrong layer — the pins don't even eliminate test failures.Changes
requirements/test.txt: Removecryptography<45andnh3<0.3PyPy markers. Dep constraints for a flaky optional CI target don't belong in the shared requirements file..github/workflows/python-package.yml: Restructuretest-pypyto degrade gracefully at the step level:Install dependenciesgetsid: install+continue-on-error: true— install failures no longer cascadeRun testsandEnforce coveragegainif: steps.install.outcome == 'success'— skipped cleanly if install fails, no spurious errorsThe job already carries
continue-on-error: trueat the job level and is excluded from the requiredcheck(needs: [lint, test-pytest]), so any PyPy failure — install or test — is fully non-blocking.