test: add large PR review harness#385
Merged
Merged
Conversation
d2ff84e to
74ba978
Compare
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.
Closes #375.
Summary
scripts/verify-large-pr-review.shfor large-PR no-post review regression checkscr review --jsonextraction--self-testfor credential-free positive and negative invariant checksVerification
rtk scripts/verify-large-pr-review.sh --helprtk scripts/verify-large-pr-review.sh --self-testrtk go test ./internal/pipeline ./internal/cmd/reviewcmd ./internal/cmd/benchmarkcmd -count=1rtk make lintrtk make buildEmpirical Harness Note
The real harness mode is dry-run/no-post and isolates data/cache state while using the maintainer's normal
crconfig. I started one local real pass withCR_LARGE_PR_KEEP_TMP=1; it blocked during local runtime construction before PR fetch or LLM breadcrumbs, so I terminated that harness process tree rather than treating it as a product signal. The script now has a per-pass timeout to make that failure mode explicit.