fix(e2e): stabilize launchable smoke agent turn - #4039
Conversation
|
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 (1)
📝 WalkthroughWalkthroughPhase 6c of the smoke test now captures the openclaw agent's exit code and stderr to a temp file (always cleaned up), broadens JSON payload parsing, and reports agent rc plus truncated reply/stdout/stderr when the expected "6×7=42" check fails. ChangesPhase 6c Agent Invocation Debugging
Estimated code review effort🎯 3 (Moderate) | ⏱️ ~18 minutes
Suggested labels:
🚥 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 |
Selective E2E Results — ❌ Some jobs failedRun: 26263494667
|
Selective E2E Results — ❌ Some jobs failedRun: 26263536345
|
afe41ec to
da1293d
Compare
Selective E2E Results — ✅ All requested jobs passedRun: 26264292591
|
Summary
--thinking offWhy
The launchable smoke run already proves direct NVIDIA Endpoints and sandbox
inference.localrouting before the agent turn. The final agent-mediated probe can fail with an empty parsed reply when OpenClaw/model thinking defaults delay or alter first-turn output, and the old failure discarded stderr so the root cause was hidden.Test plan
bash -n test/e2e/test-launchable-smoke.shRelated: issue #2599
Summary by CodeRabbit