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 — gh-126255: Ignore warning about JIT being deactivated when perf support is active in `test_embed.InitConfigTests.test_initconfig_api` by mpage · Pull Request #126302 · python/cpython Conversation
|
|
@Fidget-Spinner - Is there a way I can trigger the JIT tests on this? |
Sorry, something went wrong.
There was an error while loading. Please reload this page.
There was an error while loading. Please reload this page.
Unfortunately there's no way to trigger the JIT tests. The only way to do this - add change to JIT-related files (for example a newline) |
Sorry, something went wrong.
There was an error while loading. Please reload this page.
|
It seems that we still need a couple of changes from #126166 to solve this |
Sorry, something went wrong.
There was an error while loading. Please reload this page.
Co-authored-by: Ken Jin <[email protected]> Co-authored-by: Pablo Galindo <[email protected]>
|
I'm pushing this forward because I want to see JIT CI green 🙂 |
Sorry, something went wrong.
There was an error while loading. Please reload this page.
| 'perf_profiling': 2, | ||
| } | ||
| config_dev_mode(preconfig, config) | ||
| using_jit = any(x.startswith("JIT") for x in get_build_info()) |
There was a problem hiding this comment.
The reason will be displayed to describe this comment to others. Learn more.
Unfortunately this won't work for --enable-experimental-jit=interpreter since it doesn't raise a warning about perf profiling support (because there's no conflict with tier 2 and perf profiler)
Sorry, something went wrong.
There was an error while loading. Please reload this page.
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.
...and get_build_info probably does not work on Windows
Sorry, something went wrong.
There was an error while loading. Please reload this page.
f122803 to
79c966c
Compare
There was a problem hiding this comment.
The reason will be displayed to describe this comment to others. Learn more.
Looks good, thanks for the fix. Can you maybe just add a comment to the pylifcycle.c change to explain that this is because perf works fine with the tier two interpreter, so we just need to check on "real" JIT builds?
Sorry, something went wrong.
There was an error while loading. Please reload this page.
… support is active in `test_embed.InitConfigTests.test_initconfig_api` (python#126302) Temporarily ignore warnings about JIT deactivation when perf support is active. This will be reverted as soon as a way is found to determine at run time whether the interpreter was built with JIT. Currently, this is not possible on Windows. Co-authored-by: Kirill Podoprigora <[email protected]> Co-authored-by: Ken Jin <[email protected]> Co-authored-by: Pablo Galindo <[email protected]>
… support is active in `test_embed.InitConfigTests.test_initconfig_api` (python#126302) Temporarily ignore warnings about JIT deactivation when perf support is active. This will be reverted as soon as a way is found to determine at run time whether the interpreter was built with JIT. Currently, this is not possible on Windows. Co-authored-by: Kirill Podoprigora <[email protected]> Co-authored-by: Ken Jin <[email protected]> Co-authored-by: Pablo Galindo <[email protected]>
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.