-
-
Notifications
You must be signed in to change notification settings - Fork 32.1k
test_peg_generator fails on a PGO+LTO build with clang #117889
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
Comments
I can reproduce the issue on Fedora 39 with:
|
It seems like it's a regression introduced by the change: commit 1ddbeae.
|
Yes, I suspected this. Perhaps we should revert that change and just don't support the |
I still think we should keep 396b831, though. |
For git bisect, I used:
For old commits, it seems like test_ternary_operator() didn't exist, so instead I ran:
|
Reuse support.check_cflags_pgo() in test_peg_generator to check if PGO build is used or not.
The test_peg_generator check for PGO build no longer works since the variable contains a shell command:
I wrote PR gh-117893 to fix the test. |
Reuse support.check_cflags_pgo() in test_peg_generator to check if PGO build is used or not.
Reuse support.check_cflags_pgo() in test_peg_generator to check for PGO build. Log PGO_PROF_USE_FLAG in test.pythoninfo.
Reuse support.check_cflags_pgo() in test_peg_generator to check for PGO build. Log PGO_PROF_USE_FLAG in test.pythoninfo. (cherry picked from commit 64cd6fc) Co-authored-by: Victor Stinner <[email protected]>
…7895) Reuse support.check_cflags_pgo() in test_peg_generator to check for PGO build. Log PGO_PROF_USE_FLAG in test.pythoninfo. (cherry picked from commit 64cd6fc) Co-authored-by: Victor Stinner <[email protected]>
Reuse support.check_cflags_pgo() in test_peg_generator to check for PGO build. Log PGO_PROF_USE_FLAG in test.pythoninfo.
Uh oh!
There was an error while loading. Please reload this page.
Bug report
Example on aarch64 Debian Clang LTO + PGO 3.x: https://buildbot.python.org/all/#/builders/1084/builds/4019
Linked PRs
The text was updated successfully, but these errors were encountered: