CI: optional test run on a pypy 3.11 nightly build, see #1755 - #10142
Merged
Conversation
Scheduled (and manually triggerable) job that installs a pypy-3.11-nightly via actions/setup-python and runs the test suite with it. It is not part of ci.yml and it is continue-on-error, so it never blocks anything - it only reports. pypy nightlies change daily and borg's C extension code keeps running into cpyext differences, so both borg regressions and pypy regressions show up here early. No fuse extras: the fuse bindings do not support pypy, those tests skip. The unlocked development requirements are used, because the lock file pins versions/wheels for CPython. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
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
1 participant
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.
Summary
Adds an optional, non-blocking workflow that runs the test suite against a
pypy 3.11 nightly build (
actions/setup-pythonwithpython-version: pypy-3.11-nightly).workflow_dispatch, not on PRs, so it does notadd time to normal CI.
continue-on-error: true, so it never blocks anything - it only reports.development requirements (the lock file pins versions/wheels for CPython).
Why a nightly rather than a released pypy: pypy nightlies change daily, and borg's C extension
code keeps running into cpyext differences - pypy/pypy#5543, #5544, #5545, #5546, #5564 and
#5565 all came out of testing borg on pypy. This job notices breakage on either side early.
It also is what upstream suggested in pypy/pypy#5546.
Split out of #9976, so the workflow can be considered independently of the pypy code changes.
Note on merge order: on master alone the suite does not pass on pypy yet - without #9976
about 500 tests fail on the cpyext memoryview incompatibility (pypy/pypy#5564), so this job
would report a red run until #9976 is merged. It is
continue-on-error, so nothing is blockedeither way, but merging this after #9976 avoids the noise.
See #1755.