PYTHON-5300 - Fix unraisable error failure for test_infinite_loop_exc…

[NoahStapp]

…eeds_max_recursion_depth

PYTHON-5300

Changes in this PR

The test_infinite_loop_exceeds_max_recursion_depth test can occasionally fail if garbage collection happens while the stack is exhausted. This can cause an unraisable RecursionError which fails the test. This PR fixes the issue by disabling GC during the intentional recursion exhaustion.

Test Plan

Test changes.

Checklist

Checklist for Author

• Did you update the changelog (if necessary)?
• Is there test coverage?
• Is any followup work tracked in a JIRA ticket? If so, add link(s).

Checklist for Reviewer

• Does the title of the PR reference a JIRA Ticket?
• Do you fully understand the implementation? (Would you be comfortable explaining how this code works to someone else?)
• Is all relevant documentation (README or docstring) updated?

[Copilot]

Pull request overview

Fixes intermittent failures in test_infinite_loop_exceeds_max_recursion_depth by preventing garbage collection from running while the call stack is intentionally exhausted (which can otherwise trigger an unraisable RecursionError and fail the test suite).

Changes:

• Add gc usage to proactively gc.collect() and temporarily gc.disable() during the recursion-exhaustion portion of the test.
• Apply the same test fix to both asynchronous and generated synchronous test variants.

Reviewed changes

Copilot reviewed 2 out of 2 changed files in this pull request and generated 2 comments.

File	Description
test/asynchronous/test_custom_types.py	Disables GC around the intentional recursion exhaustion to prevent unraisable RecursionError flakiness.
test/test_custom_types.py	Mirrors the async test change in the synchronous/generated test file.

---

💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.

📢 Thoughts on this report? Let us know!

[blink1073]

LGTM