ci: Further increase pyleak blocking threshold to 5.0s #11
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
The initial increase to 2.0s (PR #10) still resulted in intermittent CI failures. Increasing to 5.0s to provide more headroom for slower GitHub Actions runners while still catching genuine blocking issues.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Summary
Further increases the pyleak blocking threshold from 2.0s to 5.0s to address intermittent CI failures.
Problem
PR #10 increased the threshold from 0.5s to 2.0s, which improved CI reliability but still resulted in occasional failures on slower GitHub Actions runners.
Solution
Increase
--blocking-thresholdfrom 2.0s to 5.0s, providing 10x the original tolerance while still catching genuine blocking issues.Changes
.github/workflows/ci.yml: Updated pytest command from--blocking-threshold=2.0to--blocking-threshold=5.0Testing
Impact