Skip to content

Conversation

@pablogsal
Copy link
Member

@pablogsalpablogsal commented Apr 4, 2021

@pablogsalpablogsal changed the title Add CI step to check changes in the exported ABIbpo-43725: Add CI step to check changes in the exported ABIApr 4, 2021
@pablogsalpablogsalforce-pushed the abicheck branch 6 times, most recently from 311b675 to 953b0f1CompareApril 4, 2021 20:55
@pablogsal
Copy link
MemberAuthor

Unfortunately seems that doing this check with two different compiler versions produce some different DWARF and the tool identifies the differences as errors :(

Copy link
Member

@gpsheadgpshead left a 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.

@pablogsalpablogsal reopened this Apr 4, 2021
@pablogsal
Copy link
MemberAuthor

I will try to investigate how to overcome this:

Unfortunately seems that doing this check with two different compiler versions produce some different DWARF and the tool identifies the differences as errors :(

@pablogsal
Copy link
MemberAuthor

@gpshead Check my message in https://bugs.python.org/msg390213 with the analysis of this solution.

check_abi:
name: 'Check if the ABI has changed'
runs-on: ubuntu-latest
Copy link
Contributor

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.

Sign up for freeto join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants

@pablogsal@gpshead@erlend-aasland@the-knights-who-say-ni@bedevere-bot