Repository navigation
ci(e2e): adopt OpenClaw lifecycle budget exception - #12718
prekshivyas wants to merge 6 commits into
Conversation
Signed-off-by: Prekshi Vyas <prekshiv@nvidia.com>
|
Auto-sync is disabled for draft pull requests in this repository. Workflows must be run manually. Contributors can view more details about this message here. |
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configuration
📒 Files selected for processing (1)
Included review availability: This review used your included allowance. Your plan provides up to 12 included reviews per hour; 11 remain after this review. 📝 WalkthroughWalkthroughThe assertion-growth policy now documents PR ChangesAssertion-growth policy
Priority: ⬇️ Low Estimated code review effort: 1 (Trivial) | ~5 minutes Change: Other Suggested reviewers: Merge Risk: ⚪ Minimal · up to This adds a narrowly scoped CI exception, with no concrete merge-blocking risk established. Whether it enables PR 🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✨ Finishing Touches🧪 Generate unit tests (beta)
Comment |
Code Coverage OverviewLanguages: TypeScript TypeScript / code-coverage/pluginThe overall line coverage in commit e303287 in the Show a line coverage summary of the most impacted files.
TypeScript / code-coverage/cliThe overall line coverage in commit e303287 in the Show a line coverage summary of the most impacted files.
Updated |
Signed-off-by: Prekshi Vyas <prekshiv@nvidia.com>
Signed-off-by: Prekshi Vyas <prekshiv@nvidia.com>
Signed-off-by: Prekshi Vyas <prekshiv@nvidia.com>
Signed-off-by: Prekshi Vyas <prekshiv@nvidia.com>
Consume the merged test-loader dependency for canonical publication validation. Preserve every exception and budget digest. Limit the added comment to the PR 12382 transition and trusted-base prerequisite. Signed-off-by: Prekshi Vyas <prekshiv@nvidia.com>
|
PR Review Advisor finished for commit Request review only when Require no Advisor blockers is green. |
senthilr-nv
left a comment
There was a problem hiding this comment.
Review of commit e30328746ef0c3ee9f26cacc2e2b52ae529af5b3
Product scope: Accepted CI-policy prerequisite for PR #12382. The signed maintainer record and the current maintain role establish the decision. This PR adds no supported runtime surface.
Review verdict: APPROVE. I found no blocking correctness, security, architecture, documentation, or data-safety finding. The new record binds PR #12382 to one exact base budget and one exact candidate budget. I recomputed both SHA-256 values from the Git objects. All previous exception records remain present. The independent guardrail reads trusted-base policy and requires the event PR number and both budget digests, so candidate policy cannot approve its own transition. PR #12718 must land before PR #12382 uses this exception. The comment states that order and the removal condition.
Security review: PASS in all nine categories:
- Secrets and credentials: no credential path or value changes.
- Input validation and data sanitization: the existing parser requires a positive PR number and 64-character lowercase SHA-256 values.
- Authentication and authorization: independent enforcement uses the trusted-base policy and event PR number.
- Dependencies and third-party libraries: no dependency changes.
- Error handling and logging: malformed policy throws; unmatched growth remains a violation.
- Cryptography and data protection: SHA-256 binds exact budget bytes; no key or protected-data flow changes.
- Configuration and security headers: only one bounded CI-policy record changes; runtime controls remain unchanged.
- Security testing: parser tests cover wrong PR, changed digests, candidate-only policy, and malformed policy.
- System security: the
pull_request_targetjob runs trusted code and treats PR commits as inert Git objects.
Validation: 65 focused growth-guardrail tests passed with NEMOCLAW_GROWTH_BASE_REF set to the PR base commit b95c0be84e061ba781fedca55e3c1e47af8dcfe1. CodeRabbit and all nine Advisor reports for this commit have no actionable finding. The cross-issue scan found no candidate issue. All six PR commits are GitHub Verified and carry DCO trailers. Feedback collection reached terminal pagination: 4 issue comments, 0 submitted reviews, 0 inline comments, and 0 threads.
Required CI: The live ruleset's checks, commit-lint, dco-check, and check-hash contexts passed on this commit. changes has a permitted skipped result after a successful run on the same commit. Before this review, GitHub reported MERGEABLE and BLOCKED pending review; auto-merge was off.
Files reviewed: ci/e2e-assertion-growth-exceptions.json, .github/workflows/codebase-growth-guardrails.yaml, test/helpers/growth-guardrail-checks.ts, test/helpers/growth-guardrail-diff.ts, test/automation/pull-requests/growth-guardrail-parsers.test.ts, test/automation/pull-requests/growth-guardrails.test.ts, and test/README.md.
Outcome
Records the maintainer-approved trusted-base exception needed for PR #12382's OpenClaw lifecycle E2E repair. After maintainer adoption on
main, the independent growth check can accept only that PR's recorded budget transition.Reason
The repaired survival and rebuild tests must obtain native admin approval before privileged fixture mutations. Survival must also check that native plugin installation succeeded. These changes retain the existing lifecycle assertions and add one unique assertion point and one generated probe condition.
The independent check reads its exception policy from the PR base. An entry only in #12382 cannot satisfy that check. This prerequisite makes the proposed exception reviewable independently of the runtime upgrade.
Changes
fdc4a78b5588629e26b00778d1bc82d69101077b9e372f2b58670510184579c2to candidate budget SHA-256f6b269053d39aefe84637914486f75853e0aa8f9e4588175c2353e3835185ec9.Verification
e2eAssertionBudgetGrowthViolationsconsumer against the real base and candidate budget bytes. The proposed trusted-base policy accepted the specified transition.Review notes
Prekshi Vyas (@prekshivyas) explicitly approved refreshing this exact budget transition in the task session on October 7, 2026. GitHub's repository permission API confirms the
maintainrole. The approval is recorded in verified signed commit 435cf418. This records the existing authorization; it is not a formal independent GitHub approval review.PR #12718 is the separate trusted-base prerequisite for #12382. This PR changes no assertion budget. Its exception must land on
mainbefore the independent check for #12382 can use it.Advisor run 37725477461 completed all nine specialists. The policy comment now states only the digest-bound transition, the trusted-base requirement, and removal after #12382 merges. Approval evidence remains in this review record. The verification finding described a candidate-only exception in #12382; this separate prerequisite implements its recommended landing order. Neither independent enforcement nor any budget digest changed.
Candidate
e30328746ef0c3ee9f26cacc2e2b52ae529af5b3includes the merged test-loader dependency from #12713 so publication uses the canonical validation surface. All 58 existing growth-parser tests passed, including wrong-PR, changed-digest and candidate-only-policy rejection. CI run 37726737536 passed. Advisor run 37728270809 completed all nine specialists with no findings. All findings, summaries, and E2E recommendations were read; no additional live E2E applies to this policy-only change.Adoption on
mainremains required before #12382 can satisfy the independent growth check. Independent review and merge remain outstanding.Signed-off-by: Prekshi Vyas prekshiv@nvidia.com
Summary by CodeRabbit