Repository navigation
Conversation
This was referenced Nov 12, 2026
DABH
marked this pull request as ready for review
November 13, 2026 05:57
Add pytest-timeout with a 300 second limit to the root project and the standalone samples, so a stuck test fails with a stack dump and the job finishes instead of sitting at the 30 minute limit with no trace.
With fail-fast on, one flaky job cancels the rest and hides whether they would have passed, which has made this week's stalls harder to read.
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
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.
This PR adds
pytest-timeoutwith a 300 second per-test limit to the root project and to the standalone sample projects. I was trying to debug stalling tests and it was very annoying to wait 30min to see a stall happen. This seems better and more debuggable.