| FazBrowse GitHub Viewer | Trending | | Home |
| Tools: [Download Repo ZIP] [Original HTTPS Page] |
Sorry, something went wrong.
The free-threaded build currently immortalizes some objects once the first thread is started. This can lead to test failures depending on the order in which tests are run. This PR addresses those failures by suppressing immortalization or skipping the affected tests.
Sorry, something went wrong.
There was a problem hiding this comment.
LGTM!
Sorry, something went wrong.
|
I still have: ======================================================================
ERROR: test_builtin_with_more_than_four_children (test.test_pydoc.test_pydoc.PydocDocTest.test_builtin_with_more_than_four_children)
Tests help on builtin object which have more than four child classes.
----------------------------------------------------------------------
Traceback (most recent call last):
File ".../cpython/Lib/test/test_pydoc/test_pydoc.py", line 537, in test_builtin_with_more_than_four_children
text = doc.docclass(object)
File ".../cpython/Lib/pydoc.py", line 1424, in docclass
subclasses = sorted(
(str(cls.__name__) for cls in type.__subclasses__(object)
if not cls.__name__.startswith("_") and cls.__module__ == "builtins"),
key=str.lower
)
File ".../cpython/Lib/pydoc.py", line 1426, in <genexpr>
if not cls.__name__.startswith("_") and cls.__module__ == "builtins"),
^^^^^^^^^^^^^^
File ".../cpython/Lib/test/test_inspect/test_inspect.py", line 775, in __module__
raise AttributeError
AttributeError: . Did you mean: '__reduce__'?
----------------------------------------------------------------------
Ran 108 tests in 1.709s
FAILED (errors=1, skipped=3)
test test.test_pydoc.test_pydoc failed
======================================================================
FAIL: test_bug1055820c (test.test_gc.GCTogglingTests.test_bug1055820c)
----------------------------------------------------------------------
Traceback (most recent call last):
File ".../cpython/Lib/test/test_gc.py", line 1361, in test_bug1055820c
self.fail("gc didn't happen after 10000 iterations")
~~~~~~~~~^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
AssertionError: gc didn't happen after 10000 iterations
======================================================================
FAIL: test_bug1055820d (test.test_gc.GCTogglingTests.test_bug1055820d)
----------------------------------------------------------------------
Traceback (most recent call last):
File ".../cpython/Lib/contextlib.py", line 85, in inner
return func(*args, **kwds)
File ".../cpython/Lib/test/test_gc.py", line 1429, in test_bug1055820d
self.fail("gc didn't happen after 10000 iterations")
~~~~~~~~~^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
AssertionError: gc didn't happen after 10000 iterations
----------------------------------------------------------------------
Ran 49 tests in 14.476s
FAILED (failures=2, skipped=4)
test test_gc failed
Not sure if the pydoc thing is related, but the gc might. |
Sorry, something went wrong.
|
The pydoc failure is a funny interaction between tests. In test_inspect.py, we create a class that raises an error when you access __module__: cpython/Lib/test/test_inspect/test_inspect.py Lines 771 to 775 in 98ff3f6 In the free-threaded build, this class is now immortalized so it's still alive later on when test_pydoc tries to generate the pydoc for all subclasses of object. |
Sorry, something went wrong.
|
Ok, I think the test_pydoc and test_gc failures are fixed now too. |
Sorry, something went wrong.
|
Thanks @colesbury for the PR 🌮🎉.. I'm working now to backport this PR to: 3.13. |
Sorry, something went wrong.
…ly (pythonGH-118864) The free-threaded build currently immortalizes some objects once the first thread is started. This can lead to test failures depending on the order in which tests are run. This PR addresses those failures by suppressing immortalization or skipping the affected tests. (cherry picked from commit b309c8e) Co-authored-by: Sam Gross <colesbury@gmail.com>
|
GH-118927 is a backport of this pull request to the 3.13 branch. |
Sorry, something went wrong.
…lly (GH-118864) (#118927) The free-threaded build currently immortalizes some objects once the first thread is started. This can lead to test failures depending on the order in which tests are run. This PR addresses those failures by suppressing immortalization or skipping the affected tests. (cherry picked from commit b309c8e) Co-authored-by: Sam Gross <colesbury@gmail.com>
|
This is the only one I got now: ======================================================================
ERROR: test_expr_context (test.test_ast.ASTConstructorTests.test_expr_context)
----------------------------------------------------------------------
Traceback (most recent call last):
File ".../cpython/Lib/test/test_ast.py", line 3042, in test_expr_context
self.assertIsInstance(name.ctx, ast.Load)
^^^^^^^^
AttributeError: 'Name' object has no attribute 'ctx'
----------------------------------------------------------------------
Ran 175 tests in 0.765s
FAILED (errors=1, skipped=1)
|
Sorry, something went wrong.
|
Just checking, this is from ./python -m test -W on the 3.13 branch? Is it a debug build? |
Sorry, something went wrong.
|
Note that that AST test was only merged (and backported to 3.13) yesterday in #118854 |
Sorry, something went wrong.
|
I might have git pulled but forgot to rebuild it. Mea culpa. Trying fresh. |
Sorry, something went wrong.
|
All is good now, thank you! |
Sorry, something went wrong.
…ly (python#118864) The free-threaded build currently immortalizes some objects once the first thread is started. This can lead to test failures depending on the order in which tests are run. This PR addresses those failures by suppressing immortalization or skipping the affected tests.
| Back | FazBrowse Home | New Git URL |
The free-threaded build currently immortalizes some objects once the first thread is started. This can lead to test failures depending on the order in which tests are run. This PR addresses those failures by suppressing immortalization or skipping the affected tests.