Repository navigation
fix: restore timeouts for generated test statistics - #20
Merged
Merged
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
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.
Generated unit-test statistics could hang indefinitely because the existing test timeout was not applied. Restore a shared five-second limit and check expected panics inside that limit, so a timeout is counted as failure in both unit and integration statistics. The existing any-panic expectation is retained.
Validation: utgen build and unit tests, minimal pipeline and task scheduling regressions, and offline replay of saved candidates. Cached regression cases cover ordinary and expected-panic loops, subsequent passing tests, coverage, and source restoration without extra model requests.