python / python/cpython

test_builtin.ImmortalTests.test_immortals tests are not so immortal on i586 and 3.14.0a3

Open
#128,107 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

3.14 tests type-bug
Dominant language
Python
Stars
77.2k
Forks
35.9k
PR merge metrics
PR metrics pending

Description

Bug report

Bug description:

All test_builtin.ImmortalTests.test_immortals tests fail on openSUSE/Factory in 3.14.0a3 on i586 (32bit) platform with this error:

[ 1122s] ======================================================================
[ 1122s] FAIL: test_immortals (test.test_builtin.ImmortalTests.test_immortals) [None]
[ 1122s] ----------------------------------------------------------------------
[ 1122s] Traceback (most recent call last):
[ 1122s]   File "/home/abuild/rpmbuild/BUILD/Python-3.14.0a3/Lib/test/test_builtin.py", line 2702, in assert_immortal
[ 1122s]     self.assertEqual(sys.getrefcount(immortal), self.IMMORTAL_REFCOUNT)
[ 1122s]     ~~~~~~~~~~~~~~~~^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[ 1122s] AssertionError: 1342177280 != 1879048192

Complete build log with all details of packages used and steps taken to reproduce.

CPython versions tested on:

3.14

Operating systems tested on:

Linux

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with Lib/test/test_builtin.py around line 2702 and the failing ImmortalTests.test_immortals assertion. Review the linked complete build log for the i586 environment and determine why the observed refcount differs from the expected value; done means the immortal tests pass on the reported 32-bit Python 3.14 build.

Written by the indexing model from the issue text.

Assessment

Tech stack
python
Domain
testing
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.