[3.14] gh-120158: Fix inconsistent monitoring state when setting events too frequently (gh-141845) #141879
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.
If we overflowed the global version counter (i.e., after 2*24 calls to
_PyMonitoring_SetEvents), we bailed out after setting global monitoringevents but before instrumenting code objects, which led to assertion errors
later on.
Also add a
time.sleep()totest_free_threading.test_monitoringto avoidoverflowing the global version counter.
(cherry picked from commit e457d60)
Co-authored-by: Sam Gross colesbury@gmail.com
test_free_threading.test_monitoring.SetProfileMultiThreaded.test_instrumentation#120158