diff options
author | Miss Islington (bot) <31488909+miss-islington@users.noreply.github.com> | 2023-05-23 08:10:44 (GMT) |
---|---|---|
committer | GitHub <noreply@github.com> | 2023-05-23 08:10:44 (GMT) |
commit | ac12a6bf34e8fb55958f027444f58016aa9600ea (patch) | |
tree | d3bbe15c6e284a1094bb29074dbaa8ba972232a0 /Lib/enum.py | |
parent | be20e9c6470775b7900a735c23afb3675354b146 (diff) | |
download | cpython-ac12a6bf34e8fb55958f027444f58016aa9600ea.zip cpython-ac12a6bf34e8fb55958f027444f58016aa9600ea.tar.gz cpython-ac12a6bf34e8fb55958f027444f58016aa9600ea.tar.bz2 |
[3.11] gh-103726: Set up gcc-10 for ASAN (gh-103728) (#104794)
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 83305808000e03cbad31ac3e9ef65454fb409282)
Co-authored-by: Dong-hee Na <donghee.na@python.org>
Diffstat (limited to 'Lib/enum.py')
0 files changed, 0 insertions, 0 deletions