-
-
Notifications
You must be signed in to change notification settings - Fork 31.8k
Unit test test_incremental_gc_handles_fast_cycle_creation sometimes fails #133532
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
There seems to be some non-linear behavior happening. Creating a few thousand extra container objects (I used empty lists) before running the test results in the following.
A log curve seems to fit the data pretty closely. |
The larger the heap, the longer it takes to scan it, so there's more lag in collecting cycles. That's my guess. |
nascheme
added a commit
to nascheme/cpython
that referenced
this issue
May 7, 2025
AA-Turner
added a commit
to nascheme/cpython
that referenced
this issue
May 8, 2025
nascheme
added a commit
to nascheme/cpython
that referenced
this issue
May 8, 2025
nascheme
added a commit
that referenced
this issue
May 8, 2025
This makes the test more reliable since there are not extra objects on the heap leftover from other tests.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Bug report
Bug description:
On a debug build on Linux AMD64, this fails for me:
The exact set of tests required before
test_gc
seems to depend on other factors. More reliable command might be:CPython versions tested on:
CPython main branch
Operating systems tested on:
Linux
Linked PRs
The text was updated successfully, but these errors were encountered: