test: stabilize installer Docker bootstrap tests on WSL#3899
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)
📝 WalkthroughWalkthroughThe test harness for Linux Docker bootstrap now injects an ChangesDocker Bootstrap Test WSL Override
Estimated code review effort🎯 1 (Trivial) | ⏱️ ~3 minutes Possibly related PRs
Suggested labels
Suggested reviewers
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)
Warning There were issues while running some tools. Please review the errors and either fix the tool's configuration or disable the tool if it's a critical failure. 🔧 ESLint
ESLint skipped: no ESLint configuration detected in root package.json. To enable, add Comment |
|
✨ Related open PRs: |
ericksoa
left a comment
There was a problem hiding this comment.
Approved after adversarial review of the test-only installer harness change. Verified the override is scoped to the sourced test subprocess, production installer behavior is unchanged, GitHub checks are green, and local focused plus full install-preflight Vitest coverage passed.
Summary
Why
PR #3824 broadened WSL detection from WSL env vars to
/procprobes viais_wsl_host. That is correct for runtime behavior, but these unit tests are specifically validating Linux Docker bootstrap branches with stubbeddocker,id,sudo, andsystemctl. On the real WSL main-watch runner,/procidentifies WSL, soensure_dockerreturns before touching the stubs and the tests fail with empty output.This overrides
is_wsl_hostinside that sourced-test harness only, so the tests keep validating the intended Linux branches on every host.Test plan
npm ci --ignore-scriptsnpx vitest run test/install-preflight.test.ts --testNamePattern "installer Docker bootstrap" --testTimeout 60000Fixes the WSL-only failures in
CI / Platform Vitest Main Watchafter #3824.Summary by CodeRabbit