-
-
Notifications
You must be signed in to change notification settings - Fork 32.1k
[Free Threading] test_builtin.ImmortalTests fail on i686 (32-bit) #128058
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
test_tuple_repeat_respect_immortality
, test_immortals
during the freethreading-debug build on i686test_{tuple,list}_repeat_respect_immortality
, test_immortals
during the freethreading-debug build on i686
I think this is probably because there's a different reference count for heap immortals and static immortals now (#127797). Does this occur on non-free-threaded builds? cc @markshannon |
On 32-bit systems, _Py_IMMORTAL_INITIAL_REFCNT is defined as 5 << 28, not 7 << 28.
Free Threading uses a different value for immortal objects. |
I created PR gh-128068 to fix this regression. |
test_{tuple,list}_repeat_respect_immortality
, test_immortals
during the freethreading-debug build on i686On 32-bit Free Threading systems, immortal reference count is 5 << 28, instead of 7 << 28. Co-authored-by: Peter Bierma <[email protected]>
On 32-bit Free Threading systems, immortal reference count is 5 << 28, instead of 7 << 28. Co-authored-by: Peter Bierma <[email protected]>
On 32-bit Free Threading systems, immortal reference count is 5 << 28, instead of 7 << 28. Co-authored-by: Peter Bierma <[email protected]>
Uh oh!
There was an error while loading. Please reload this page.
Bug report
Bug description:
In Fedora Linux, when building 3.14.0a3 on i686 architecture and freethreading-debug build,
test_tuple_respect_immortality
,test_list_repeat_respect_immortality
andtest_immortals
fail.This is not happening on x86_64, aarch64. We don't know about the other arches yet.
CPython versions tested on:
3.14
Operating systems tested on:
Linux
Linked PRs
The text was updated successfully, but these errors were encountered: