GeezerVison is showing github.com — gh-95756: Lazily created cached co_* attrs by Fidget-Spinner · Pull Request #97791 · python/cpython
Conversation
As long as these aren't accessed, they don't actually consume additional space over 3.11.
Sorry, something went wrong.
Uh oh!
There was an error while loading. Please reload this page.
Sorry, something went wrong.
Uh oh!
There was an error while loading. Please reload this page.
|
I'd like to reduce the size of code objects for a few reasons. PEP 649 will create lots of small code objects and we want multiple interpreters to share as much data as possible.
|
Sorry, something went wrong.
Uh oh!
There was an error while loading. Please reload this page.
|
I'm merging this, as we can add the line array, and any other tables needed in unusual cases, to the _co_cached structs.
In other words, this will save space.
|
Sorry, something went wrong.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
|
When you're done making the requested changes, leave the comment: I have made the requested changes; please review again.
|
Sorry, something went wrong.
Uh oh!
There was an error while loading. Please reload this page.
|
|
if (*cached_field != NULL) {
|
|
|
return Py_NewRef(*cached_field);
|
|
|
}
|
|
|
assert(*cached_field == NULL);
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
No need to assert this. The test two lines above ensures that it is true.
Sorry, something went wrong.
Uh oh!
There was an error while loading. Please reload this page.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
One assert that could be removed, but it's harmless.
Sorry, something went wrong.
Uh oh!
There was an error while loading. Please reload this page.
|
I'll leave the assert in since it communicates some info should the code change in the future. And like you mentioned it's harmless anyways.
|
Sorry, something went wrong.
Uh oh!
There was an error while loading. Please reload this page.
⚠️⚠️⚠️ Buildbot failure ⚠️⚠️⚠️
Hi! The buildbot ARM64 macOS 3.x has failed when building commit b399115.
What do you need to do:
- Don't panic.
- Check the buildbot page in the devguide if you don't know what the buildbots are or how they work.
- Go to the page of the buildbot that failed (https://buildbot.python.org/all/#builders/725/builds/2786) and take a look at the build logs.
- Check if the failure is related to this commit (b399115) or if it is a false positive.
- If the failure is related to this commit, please, reflect that on the issue and make a new Pull Request with a fix.
You can take a look at the buildbot page here:
https://buildbot.python.org/all/#builders/725/builds/2786
Failed tests:
Summary of the results of the build (if available):
==
Click to see traceback logs
remote: Enumerating objects: 30, done.
remote: Counting objects: 3% (1/30)
remote: Counting objects: 6% (2/30)
remote: Counting objects: 10% (3/30)
remote: Counting objects: 13% (4/30)
remote: Counting objects: 16% (5/30)
remote: Counting objects: 20% (6/30)
remote: Counting objects: 23% (7/30)
remote: Counting objects: 26% (8/30)
remote: Counting objects: 30% (9/30)
remote: Counting objects: 33% (10/30)
remote: Counting objects: 36% (11/30)
remote: Counting objects: 40% (12/30)
remote: Counting objects: 43% (13/30)
remote: Counting objects: 46% (14/30)
remote: Counting objects: 50% (15/30)
remote: Counting objects: 53% (16/30)
remote: Counting objects: 56% (17/30)
remote: Counting objects: 60% (18/30)
remote: Counting objects: 63% (19/30)
remote: Counting objects: 66% (20/30)
remote: Counting objects: 70% (21/30)
remote: Counting objects: 73% (22/30)
remote: Counting objects: 76% (23/30)
remote: Counting objects: 80% (24/30)
remote: Counting objects: 83% (25/30)
remote: Counting objects: 86% (26/30)
remote: Counting objects: 90% (27/30)
remote: Counting objects: 93% (28/30)
remote: Counting objects: 96% (29/30)
remote: Counting objects: 100% (30/30)
remote: Counting objects: 100% (30/30), done.
remote: Compressing objects: 6% (1/15)
remote: Compressing objects: 13% (2/15)
remote: Compressing objects: 20% (3/15)
remote: Compressing objects: 26% (4/15)
remote: Compressing objects: 33% (5/15)
remote: Compressing objects: 40% (6/15)
remote: Compressing objects: 46% (7/15)
remote: Compressing objects: 53% (8/15)
remote: Compressing objects: 60% (9/15)
remote: Compressing objects: 66% (10/15)
remote: Compressing objects: 73% (11/15)
remote: Compressing objects: 80% (12/15)
remote: Compressing objects: 86% (13/15)
remote: Compressing objects: 93% (14/15)
remote: Compressing objects: 100% (15/15)
remote: Compressing objects: 100% (15/15), done.
remote: Total 16 (delta 14), reused 2 (delta 1), pack-reused 0
From https://github.com/python/cpython
* branch main -> FETCH_HEAD
Note: switching to 'b399115ef18945f7526492225d72a512048ad20d'.
You are in 'detached HEAD' state. You can look around, make experimental
changes and commit them, and you can discard any commits you make in this
state without impacting any branches by switching back to a branch.
If you want to create a new branch to retain commits you create, you may
do so (now or later) by using -c with the switch command. Example:
git switch -c <new-branch-name>
Or undo this operation with:
git switch -
Turn off this advice by setting config variable advice.detachedHead to false
HEAD is now at b399115ef1 gh-95756: Lazily created cached co_* attrs (GH-97791)
Switched to and reset branch 'main'
Configured with: --prefix=/Library/Developer/CommandLineTools/usr --with-gxx-include-dir=/Library/Developer/CommandLineTools/SDKs/MacOSX.sdk/usr/include/c++/4.2.1
configure: WARNING: ffi.h: accepted by the compiler, rejected by the preprocessor!
configure: WARNING: ffi.h: proceeding with the compiler's result
configure: WARNING: pkg-config is missing. Some dependencies may not be detected correctly.
Fatal Python error: Fatal Python error: Segmentation faultSegmentation fault
Thread 0x000000028301f000 (most recent call first):
File "/Users/buildbot/buildarea/3.x.pablogsal-macos-m1.macos-with-brew/build/Lib/test/test_syslog.py", line 67 in logger
File "/Users/buildbot/buildarea/3.x.pablogsal-macos-m1.macos-with-brew/build/Lib/threading.py", line 986 in run
File "/Users/buildbot/buildarea/3.x.pablogsal-macos-m1.macos-with-brew/build/Lib/threading.py", line 1049 in _bootstrap_inner
File "/Users/buildbot/buildarea/3.x.pablogsal-macos-m1.macos-with-brew/build/Lib/threading.py", line 1006 in _bootstrap
Thread 0x0000000282013000make: *** [buildbottest] Segmentation fault: 11
Cannot open file '/Users/buildbot/buildarea/3.x.pablogsal-macos-m1.macos-with-brew/build/test-results.xml' for upload
|
Sorry, something went wrong.
Uh oh!
There was an error while loading. Please reload this page.
|
I'm confused. Why is this the only buildbot failing? In any case I might revert this within 24 hours.
|
Sorry, something went wrong.
Uh oh!
There was an error while loading. Please reload this page.
I'm confused. Why is this the only buildbot failing? In any case I might revert this within 24 hours.
I created #98178 about this crash. It seems to be specific to macOS and unrelated to your change. If your change would introduce a bug, more tests would crash on more platforms.
|
Sorry, something went wrong.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Assignees
No one assigned
Milestone
No milestone
Development
Successfully merging this pull request may close these issues.
Uh oh!
There was an error while loading. Please reload this page.
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
|