test(docx-compare): preserve verifier integration timeout - #778
Merged
Conversation
The verified CLI intentionally lowers the production verifier default from 120 seconds to 10 seconds, but the corpus-scale extraction-limit tests accidentally inherited that tighter runtime budget. GitHub's slower runner crossed the limit while constructing an expected failure certificate, making lean-build flaky even though the proof and checker were correct.\n\nGive only the compiled real-checker test helpers their historical 120-second allowance. Dedicated timeout tests continue to set short explicit budgets, while the CLI and library production default remain 10 seconds.\n\nRef: #777
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
stevenobiajulu
enabled auto-merge (squash)
July 30, 2026 19:58
Aggregate and post reviewOverall: PASS (5 pass, 0 warn, 0 error, 12 skipped, 17 total)
|
stevenobiajulu
disabled auto-merge
July 30, 2026 20:06
Codecov Report✅ All modified and coverable lines are covered by tests. 📢 Thoughts on this report? Let us know! |
Member
Author
|
Post-merge smoke: PASS
No confidential documents or identifying corpus data were used or published. |
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.
Summary
Why
PR #776 intentionally lowered the production default from 120 seconds to 10 seconds. The Lean CI runner then timed out a near-envelope test at 10.264 seconds before it could return the expected failed certificate. This patch separates the integration-test budget from the product default.
Validation
Ref: #777