Repository navigation
Conversation
Build CPython main on Ubuntu and macOS and run `relocatable.py test` with both strategies, daily and for each push and pull request. On macOS, the libraries that the system doesn't provide are built with `relocatable.py deps`. Failed checks don't fail the job, since some fail until CPython is fixed; the results go in the job summary and an uploaded JSON artifact. The job fails only if the build or the harness itself breaks. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This was referenced Nov 5, 2026
Contributor
Author
|
@brettcannon I think GHA is not enabled for this repo. do you have access to enable it? |
hugovk
reviewed
Nov 5, 2026
Comment on lines
+9
to
+10
| push: | ||
| branches: [main] |
Member
There was a problem hiding this comment.
Allow forks to run CI on feature branches, so we can check results on our fork CI before opening a PR.
Suggested change
| push: | |
| branches: [main] | |
| push: |
| test: | ||
| name: ${{ matrix.os }} | ||
| # Forks get the schedule too; only run it here. | ||
| if: github.event_name != 'schedule' || github.repository == 'python/prebuilt-cpython' |
Member
There was a problem hiding this comment.
Same thing without hardcoding repo name, easier to copy to other repos:
Suggested change
| if: github.event_name != 'schedule' || github.repository == 'python/prebuilt-cpython' | |
| if: github.event_name != 'schedule' || github.event.repository.fork == false |
| with: | ||
| path: prebuilt-cpython | ||
| persist-credentials: false | ||
| - uses: actions/checkout@v5 |
Member
There was a problem hiding this comment.
Suggested change
| - uses: actions/checkout@v5 | |
| - uses: actions/checkout@v7 |
| matrix: | ||
| os: [ubuntu-latest, macos-latest] | ||
| steps: | ||
| - uses: actions/checkout@v5 |
Member
There was a problem hiding this comment.
Suggested change
| - uses: actions/checkout@v5 | |
| - uses: actions/checkout@v7 |
| repository: python/cpython | ||
| path: cpython | ||
| persist-credentials: false | ||
| - uses: actions/setup-python@v6 |
Member
There was a problem hiding this comment.
Suggested change
| - uses: actions/setup-python@v6 | |
| - uses: actions/setup-python@v7 |
| persist-credentials: false | ||
| - uses: actions/setup-python@v6 | ||
| with: | ||
| python-version: "3.14" |
Member
There was a problem hiding this comment.
Do we specifically need 3.14, or can we use 3.15?
Suggested change
| python-version: "3.14" | |
| python-version: "3.15" |
Or whatever the latest stable is?
Suggested change
| python-version: "3.14" | |
| python-version: "3.x" |
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.
This adds a workflow that builds CPython
mainon Ubuntu and macOS and runsrelocatable.py testwith both--strategy patchand--strategy origin. It serves as a "progress tracker" as well as a "burndown list" of relocatability gaps.Some checks fail until CPython is fixed, so failed checks don't fail the job. Each run's summary has a table of the results, and the JSON output is uploaded as an artifact. The job fails only if the build or the harness itself breaks.
The daily run only happens in this repository, not in forks.
Test run
I ran this workflow in my fork (run, from this PR).
Both jobs passed: Linux took ~3m and macOS ~5m.
Both strategies gave the same results on each platform:
Written with assistance from Claude Opus 5.5