python / python/cpython

test_class.test_detach_materialized_dict_no_memory() fails randomly on the Free Threading macOS CI

Open
#157,429 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

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

Description

macOS (free-threading) / build and test (macos-26) build: https://github.com/python/cpython/actions/runs/34757893189/job/103725487469?pr=157417

FAIL: test_detach_materialized_dict_no_memory (test.test_class.TestInlineValues.test_detach_materialized_dict_no_memory)
----------------------------------------------------------------------
test.support.isolation._RemoteTraceback: 
"""
Traceback (most recent call last):
  File "/Users/runner/work/cpython/cpython/Lib/test/support/__init__.py", line 1374, in internal
    return test(*args, **kwargs)
AssertionError: the dictionary was not cleared
"""

The above exception was the direct cause of the following exception:

Traceback (most recent call last):
  File "/Users/runner/work/cpython/cpython/Lib/test/support/__init__.py", line 1374, in internal
    return test(*args, **kwargs)
AssertionError: test failed in the subprocess
Linked PRs
  • gh-157444

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 test.test_class.TestInlineValues.test_detach_materialized_dict_no_memory and the linked macOS free-threading CI run. Reproduce the failure on the macOS-26 free-threading build, then inspect the subprocess assertion that the dictionary was not cleared. Done means the test no longer fails randomly in that CI configuration.

Written by the indexing model from the issue text.

Assessment

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

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.