Repository navigation
fix: require actual tests in generation and prefix answers - #13
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.
A model reply such as
fn helper() {}previously parsed as Rust and let generation finish successfully with zero tests. Direct-test and prefix generation now require at least one extracted#[test]function, using a single parse/extraction pass and the existing three-attempt format retry loop. Prefixes remain valid without assertions.Each returned answer is saved before code-fence cleanup and parsing, with stage/attempt filenames under the existing answer directory. Accepted code retains its previous layout. Network retries, shared request limits, compilation checks, and existing caches are unchanged; separate trials continue to use fresh copies.
Validation: workspace build and 46 tests passed (the credentialed live test remains opt-in), along with the minimal generation/repair/coverage pipeline. Six real-CLI local-HTTP cases passed for direct-test and prefix recovery, format exhaustion, and request-budget interruption, checking saved raw replies, request/token counts, successful candidates and source restoration. The existing scheduling and failure-cleanup matrix also runs in CI. No real model request is needed for these regressions.