gh-103726: Set up gcc-10 for ASAN #103728
Merged
Conversation
This file contains 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
Member
corona10
commented
Apr 23, 2023
•
corona10
commented
- Issue: ASAN false positives due to vfork() with GCC 9 #103726
For ASAN |
|
We can update |
gpshead
approved these changes
Apr 24, 2023
hugovk
approved these changes
Apr 24, 2023
gpshead
added
needs backport to 3.10
|
Thanks @corona10 for the PR 🌮🎉.. I'm working now to backport this PR to: 3.11. |
|
Thanks @corona10 for the PR 🌮🎉.. I'm working now to backport this PR to: 3.10. |
|
Sorry, @corona10, I could not cleanly backport this to |
|
GH-104794 is a backport of this pull request to the 3.11 branch. |
miss-islington
pushed a commit
to miss-islington/cpython
that referenced
this pull request
May 23, 2023
<!-- Thanks for your contribution! Please read this comment in its entirety. It's quite important. GH- Pull Request title It should be in the following format: ``` gh-NNNNN: Summary of the changes made ``` Where: gh-NNNNN refers to the GitHub issue number. Most PRs will require an issue number. Trivial changes, like fixing a typo, do not need an issue. GH- Backport Pull Request title If this is a backport PR (PR made against branches other than `main`), please ensure that the PR title is in the following format: ``` [X.Y] <title from the original PR> (GH-NNNN) ``` Where: [X.Y] is the branch name, e.g. [3.6]. GH-NNNN refers to the PR number from `main`. --> <!-- gh-issue-number: pythongh-103726 --> * Issue: pythongh-103726 <!-- /gh-issue-number --> (cherry picked from commit 8330580) Co-authored-by: Dong-hee Na <donghee.na@python.org>
gpshead
pushed a commit
that referenced
this pull request
May 23, 2023
Set up gcc-10 for ASAN CI as the existing config's default 9.x does not play well with `vfork()`. <!-- Thanks for your contribution! Please read this comment in its entirety. It's quite important. GH- Pull Request title It should be in the following format: ``` gh-NNNNN: Summary of the changes made ``` Where: gh-NNNNN refers to the GitHub issue number. Most PRs will require an issue number. Trivial changes, like fixing a typo, do not need an issue. GH- Backport Pull Request title If this is a backport PR (PR made against branches other than `main`), please ensure that the PR title is in the following format: ``` [X.Y] <title from the original PR> (GH-NNNN) ``` Where: [X.Y] is the branch name, e.g. [3.6]. GH-NNNN refers to the PR number from `main`. --> <!-- gh-issue-number: gh-103726 --> * Issue: gh-103726 <!-- /gh-issue-number --> (cherry picked from commit 8330580) Co-authored-by: Dong-hee Na <donghee.na@python.org>
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.