test(e2e): add OpenShell version pin guard for #3474#3478
Conversation
Adds a failing regression E2E guard for the sticky OpenShell case reported in #3474. Until the fix lands, the targeted regression openshell-version-pin-e2e dispatch will fail because install-openshell.sh hard-fails when an existing openshell 0.0.40 is above NemoClaw's max supported 0.0.39 instead of reinstalling the pinned compatible release. Related: #3474
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Path: .coderabbit.yaml Review profile: CHILL Plan: Enterprise Run ID: 📒 Files selected for processing (2)
📝 WalkthroughWalkthroughThis PR adds end-to-end regression coverage for OpenShell version pinning. The workflow is extended to include a new selectable ChangesOpenShell Version Pin E2E Regression Test
Estimated code review effort🎯 3 (Moderate) | ⏱️ ~20 minutes Possibly related issues
Possibly related PRs
Suggested labels
Suggested reviewers
Poem
🚥 Pre-merge checks | ✅ 4 | ❌ 1❌ Failed checks (1 warning)
✅ Passed checks (4 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing Touches📝 Generate docstrings
🧪 Generate unit tests (beta)
Comment |
E2E Advisor RecommendationRequired E2E: None Dispatch hint: Full advisor summaryPi Semantic E2E AdvisorBase: Required E2E
Optional E2E
New E2E recommendations
Dispatch hint
|
Summary
Adds a failing-test-first regression guard for #3474 / Margaret's QA report:
openshell --versionreports0.0.40while NemoClaw's installer supports max0.0.39scripts/install-openshell.shshould recover by downloading/replacing with pinned OpenShellv0.0.39regression-e2e.yamlasopenshell-version-pin-e2eFailing-test-first note
This test is expected to fail on current main until the fix lands. Current main exits early with:
The desired fixed behavior is that the installer warns/reinstalls the pinned compatible OpenShell release instead of hard-failing on sticky
openshell 0.0.40.Regression holding pen
This job lives in
.github/workflows/regression-e2e.yamland is not part of scheduled nightly E2E. It can be dispatched explicitly with:After the fix PR lands, this guard can be reviewed for promotion or left as an explicit regression dispatch.
Related: #3474
Summary by CodeRabbit