GH-124567: Reduce overhead of debug build for GC. Should help CI performance#126777
Uh oh!
There was an error while loading. Please reload this page.
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The doctests CI takes ages and it uses a debug build.
Arguably debug builds should be good for debugging, i.e. lots of asserts. If you want performance don't use a debug build.
However, the incremental GC does adds a lot of extra sanity checks and it is a pain if CI jobs take half an hour or more.
So, this PR adds an extra debug option to reduce the amount of checking done in a normal debug build, but keeps the extra sanity checks if needed for debugging the GC.
📚 Documentation preview 📚: https://cpython-previews--126777.org.readthedocs.build/