-
-
Notifications
You must be signed in to change notification settings - Fork 31.9k
AMD64 Windows11 Bigmem 3.x: test_bigmem failed with !_Py_IsImmortal(FROM_GC(gc)) assertion error #115124
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
Replace assert() with _PyObject_ASSERT() in gc.c to dump the object when an assertion fails.
Replace assert() with _PyObject_ASSERT() in gc.c to dump the object when an assertion fails.
See also issue gh-115122: "regrtest: add --bisect option to run test.bisect_cmd on failed tests". |
@ambv message on Discord: Note: the bigmem buildbot caught an assertion failure in GC Started with https://buildbot.python.org/all/#/builders/1079/builds/3327
I'll be disabling bigmem on 3.12 as at this point it's unlikely to catch anything new in 3.12. So we'll have less waiting for the buildbot on main. |
This build contains two changes: |
See also issue gh-115127: multiprocessing test_thread_safety() fails with "gc_list_is_empty(to) || gc_old_space(to_tail) == gc_old_space(from_tail)" assert error. |
This was #108362 |
Replace assert() with _PyObject_ASSERT() in gc.c to dump the object when an assertion fails.
Replace assert() with _PyObject_ASSERT() in gc.c to dump the object when an assertion fails.
Replace assert() with _PyObject_ASSERT() in gc.c to dump the object when an assertion fails.
Replace assert() with _PyObject_ASSERT() in gc.c to dump the object when an assertion fails.
Replace assert() with _PyObject_ASSERT() in gc.c to dump the object when an assertion fails.
Replace assert() with _PyObject_ASSERT() in gc.c to dump the object when an assertion fails.
Replace assert() with _PyObject_ASSERT() in gc.c to dump the object when an assertion fails.
build: https://buildbot.python.org/all/#/builders/1079/builds/3327
Error after tests complete, when running
gc_collect()
C function:Logs:
EDIT: I created issue gh-115127 for the test_multiprocessing_spawn error.
Linked PRs
The text was updated successfully, but these errors were encountered: