-
-
Notifications
You must be signed in to change notification settings - Fork 30.9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
bpo-43725: Add CI step to check changes in the exported ABI #25188
Conversation
311b675
to
953b0f1
Compare
Unfortunately seems that doing this check with two different compiler versions produce some different DWARF and the tool identifies the differences as errors :( |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Neat, lets try it out! I suppose this shows up as a non-blocking check by default? Release branch owners can presumably decide if this is reliable enough to make it blocking.
I will try to investigate how to overcome this:
|
@gpshead Check my message in https://bugs.python.org/msg390213 with the analysis of this solution. |
@@ -48,6 +48,28 @@ jobs: | |||
git diff --name-only origin/$GITHUB_BASE_REF.. | grep -qvE '(\.rst$|^Doc|^Misc)' && echo '::set-output name=run_tests::true' || true | |||
fi | |||
|
|||
check_abi: | |||
name: 'Check if the ABI has changed' | |||
runs-on: ubuntu-latest |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'd pin the runner, to ensure that the job runs with at least the same major GCC version every time. Ref. bpo-43382.
https://bugs.python.org/issue43725