GeezerVisonThe World Wide Web, restored to 800 pixels of glory. | |||||||||||||||
| Home|About|Gaming cabinet|Archives|How it works|Starter sites | |||||||||||||||
GeezerVison is showing github.com — bpo-43725: Add CI step to check changes in the exported ABI by pablogsal · Pull Request #25188 · python/cpython Conversation
|
|
Unfortunately seems that doing this check with two different compiler versions produce some different DWARF and the tool identifies the differences as errors :( |
Sorry, something went wrong.
There was an error while loading. Please reload this page.
There was a problem 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.
Sorry, something went wrong.
There was an error while loading. Please reload this page.
|
I will try to investigate how to overcome this:
|
Sorry, something went wrong.
There was an error while loading. Please reload this page.
|
@gpshead Check my message in https://bugs.python.org/msg390213 with the analysis of this solution. |
Sorry, something went wrong.
There was an error while loading. Please reload this page.
|
|
||
| check_abi: | ||
| name: 'Check if the ABI has changed' | ||
| runs-on: ubuntu-latest |
There was a problem 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.
Sorry, something went wrong.
There was an error while loading. Please reload this page.
There was an error while loading. Please reload this page.
Successfully merging this pull request may close these issues.
There was an error while loading. Please reload this page.