-
-
Notifications
You must be signed in to change notification settings - Fork 30.7k
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
PGO tests fail on 3.11 and 3.12 #111929
Comments
test_unicode was renamed to test_str in Python 3.13, but Python 3.12 still uses test_unicode name.
test_unicode was renamed to test_str in Python 3.13, but Python 3.12 still uses test_unicode name.
…GH-111938) test_unicode was renamed to test_str in Python 3.13, but Python 3.12 still uses test_unicode name. (cherry picked from commit 5f42a2b) Co-authored-by: Victor Stinner <vstinner@python.org>
I'm working on fixes. |
How do we ensure this isn't repeated the next time we try to sync libregrtest in the backport branches with the code on the main branch? |
I'm considering to backport the Makefile change which treats a failure... as a failure: don't ignore the failure. |
I created #111950 for that. |
Thanks @neonene for your bug report! |
Bug report
Bug description:
Recent PGO tests on Python 3.11 and 3.12 result in failure.
For example, Linux Buildbots' logs (compile section) are like:
3.12 (AMD64 RHEL7 LTO + PGO)
3.11 (AMD64 RHEL7 LTO + PGO)
Seems related to issue gh-110276, gh-110756.
cc: @vstinner @AlexWaygood
CPython versions tested on:
3.12
Operating systems tested on:
Windows
Linked PRs
The text was updated successfully, but these errors were encountered: