fix(e2e): use --name flag in landlock sandbox exec (#1851) - #1934
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 (2)
✅ Files skipped from review due to trivial changes (1)
📝 WalkthroughWalkthroughReplaced positional sandbox name arguments with an explicit 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 unit tests (beta)
Comment |
ericksoa
left a comment
There was a problem hiding this comment.
Nice fix — root cause analysis and verification are really thorough, thank you!
While looking at this, I noticed test/e2e/test-sandbox-rebuild.sh also calls openshell sandbox exec "$SANDBOX_NAME" (lines 99, 104, 147) without --name. Do you think those would hit the same exit-127 on openshell 0.0.26? Might be worth a quick check — would be great to sweep them all in one pass if so.
|
✨ Possibly related open PRs: Possibly related open issues: |
04-landlock-readonly.sh has exited 127 on every nightly since it was added (April 8). The sandbox_exec() helper calls: openshell sandbox exec "$SANDBOX_NAME" -- bash -c "..." but openshell 0.0.26 requires the --name flag for positional sandbox identification. Without it, the sandbox name is parsed as the command to execute, producing 'command not found' (exit 127). Fix: openshell sandbox exec --name "$SANDBOX_NAME" -- bash -c "..." Closes #1851
Sweep the same positional-arg fix from 04-landlock-readonly.sh to test-sandbox-rebuild.sh (lines 99, 104, 147). OpenShell 0.0.26 requires --name instead of a positional sandbox name for `openshell sandbox exec`. Co-authored-by: Aaron Erickson <aerickson@nvidia.com>
58a236b to
74f2585
Compare
Summary
04-landlock-readonly.shhas exited 127 on every nightly since April 8 when it was added in PR #1121. This is one of the three root causes keeping the nightly E2E red for 24+ consecutive days.Root Cause
The
sandbox_exec()helper calls:But
openshell 0.0.26requires the--nameflag:Without
--name, the sandbox name (e2e-cloud-experimental) is parsed as the command to execute, producingcommand not found→ exit 127.Fix
One-line change in
sandbox_exec():Verification
Reproduced and verified the fix on a DGX Spark running the E2E suite:
04-landlock-readonly: EXIT CODE: 127openshell sandbox exec --name e2e-debug -- echo "hello from sandbox"→hello from sandboxCloses #1851
Summary by CodeRabbit