fix(test): tolerate version token in snapshot create success grep#2314
Conversation
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Path: .coderabbit.yaml Review profile: CHILL Plan: Pro Plus Run ID: 📒 Files selected for processing (1)
🚧 Files skipped from review as they are similar to previous changes (1)
📝 WalkthroughWalkthroughThe test script's snapshot creation success detection was relaxed: the success check now uses a regex that allows a version token between "Snapshot" and "created" (e.g., Changes
Estimated code review effort🎯 2 (Simple) | ⏱️ ~10 minutes Poem
🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing Touches📝 Generate docstrings
🧪 Generate unit tests (beta)
Comment |
|
✨ Related open PRs: Related open issues: |
Merge main into fix/nightly-e2e-repairs-v4, resolving conflicts: - nightly-e2e.yaml: keep contains(needs.*.result, 'failure') from #2371, remove cloud-experimental-e2e from notify-on-failure needs array - test-snapshot-commands.sh: keep exit-code check from this PR + tolerant grep regex from #2314 Address reviewer feedback: - Drop NEMOCLAW_RECREATE_SANDBOX from deployment-services to avoid re-introducing the delete+create race fixed in #2313 (@prekshivyas) - Update cloud-experimental-e2e disable comment: drop stale Landlock mention (fixed in OpenShell#810 v0.0.32+), reference only docs-drift (@prekshivyas) - Extract dump_diagnostics() in test-snapshot-commands.sh to centralize duplicate probes from fail() and Phase 2b (CodeRabbit)
Summary
The `test-snapshot-commands.sh` nightly E2E was failing despite `nemoclaw snapshot create` actually succeeding. The test greps for the literal string `"Snapshot created"` but the real success output includes a version token between:
```
✓ Snapshot v1 created (12 directories)
```
Grep didn't match → false red in nightly despite the command succeeding.
Switching to regex `"Snapshot v[0-9]+.*created"` that tolerates the version token.
Why found now
Investigating #2268 revealed this test reporting FAIL on a run where the operation had actually succeeded per the log. Pre-existing on main — predates both #2308 and any recent PR.
Test plan
🤖 Generated with Claude Code
Summary by CodeRabbit