Enable origin tracking for coroutine objects #6762
Merged
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.
Sometimes in tests, we have a situation when the task was created in one test or fixture and then crashed in a totally unrelated test during the garbage collection phase. In that case, we see the failed test, but not the test or fixture that was the originator of the unhandled task.
In this PR I enable the origin tracking for coroutine objects (a feature available in Python 3.7 and later).
As an example, right now I see the following error in a completely unrelated test:
With this feature enabled, I can see the traceback and discover the fixture in which the unhandled task was created: