Uh oh!
There was an error while loading.Please reload this page.
- Notifications
You must be signed in to change notification settings - Fork33.3k
GH-126892: Reset warmup counters when JIT compiling code#126893
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 ourterms of service andprivacy statement. We’ll occasionally send you account related emails.
Already on GitHub?Sign in to your account
Uh oh!
There was an error while loading.Please reload this page.
Changes from1 commit
b1d77eb351750202d4d741bb6bd0a6e173f1d8d086File filter
Filter by extension
Conversations
Uh oh!
There was an error while loading.Please reload this page.
Jump to
Uh oh!
There was an error while loading.Please reload this page.
Diff view
Diff view
- Loading branch information
Uh oh!
There was an error while loading.Please reload this page.
There are no files selected for viewing
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -91,7 +91,10 @@ def _make_error(reason, details): | ||
| res, cmd_line = run_python_until_end( | ||
| "-c", | ||
| textwrap.dedent(code), | ||
| __run_using_command=[_strace_binary] + strace_flags, | ||
| # Don't want to trace our JIT's own mmap and mprotect calls: | ||
| PYTHON_JIT="0", | ||
Contributor There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others.Learn more. Guessing this showed up in the I have been keeping an eye on / working through a couple other issues where mmap(NULL) and mprotect show up, trying to figure out if just excluding those two from that test would be good/effective (memory allocation happening in reading files is fine / not what the test is focused on). There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others.Learn more. Yeah, I was wondering if this was susceptible to catching badly-timed arena allocations and such too. Might make sense to have an option to ignore the I'm just not familiar with how this is being used, and didn't want to change the meaning/behavior of the tests too dramatically. | ||
| ) | ||
| except OSError as err: | ||
| return _make_error("Caught OSError", err) | ||
Uh oh!
There was an error while loading.Please reload this page.