Repository navigation
test(onboard): avoid host PID collisions in gateway fixture - #11934
Conversation
Signed-off-by: Julie Yaunches <jyaunches@nvidia.com>
|
Auto-sync is disabled for draft pull requests in this repository. Workflows must be run manually. Contributors can view more details about this message here. |
|
Caution Review failedThe pull request is closed. ℹ️ Recent review info⚙️ Run configurationConfiguration used: Path: .coderabbit.yaml Review profile: CHILL Plan: Enterprise Run ID: 📒 Files selected for processing (1)
📝 WalkthroughWalkthroughChangesProcess test updates
Estimated code review effort: 1 (Trivial) | ~5 minutes Change: Other Suggested reviewers: ✨ Finishing Touches 💡 1🛠️ Fix failing CI checks 💡
📝 Generate docstrings
🧪 Generate unit tests (beta)
Comment |
Code Coverage OverviewLanguages: TypeScript TypeScript / code-coverage/pluginThe overall line coverage in commit eea6f95 in the TypeScript / code-coverage/cliThe overall line coverage in commit eea6f95 in the Show a line coverage summary of the most impacted files.
Updated |
Outcome
The gateway-absence test uses a fixture PID that cannot be occupied by a normal Linux process. Its command-line assertion now consistently observes the mocked gateway.
Reason
PR #11876 CI shard 1 returned
nullwhere the test expected a live gateway. The test mockedpsfor PID 4343, but the implementation reads/proc/<pid>/cmdlinefirst. A real process with that PID can override the mock. The source and test were unchanged from base2fd6903328a66de8256f4b5b300c2ec639e1fa01.Changes
Use PID 9999434, following the high-PID convention already used by neighboring tests. Keep the PID consistent across discovery, process status, ownership, command-line responses, and the assertion. Production behavior is unchanged.
Verification
Reviewed commit:
eea6f9565d94c53bd7caa262197d6f3ecc938ec5.Normal pre-push publication validation and all three TypeScript hooks passed.
Normal signed-commit hooks passed, including formatting, lint, repository checks, secret scanning, source-shape and growth guards.
NODE_OPTIONS=--max-old-space-size=8192 npm run typecheck:cli— passed after the default heap was exhausted.Reproduced the failure mechanism: the original fixture reports a live gateway normally, but returns
nullwhen an unrelated/proc/4343/cmdlineis present.npx --no-install vitest run --project cli src/lib/onboard/host-gateway-process.test.ts— all 23 tests passed.Inspected neighboring process fixtures; they already use the high-PID convention.
git diff --check— passed. The diff contains no secrets, API keys, or credentials.CI run 35130323227: all 12 CLI shards passed, including all 23 gateway process tests; plugin tests, installer integration, static checks and type checks passed. Aggregate coverage failed on unchanged MCP lock-storage code: 54.45% branch coverage against 60%. PR #11921 contains the existing coverage repair; this PR remains draft pending that dependency.
Image workflow 35130323159 — passed, including exact published-image activation for OpenClaw, Hermes, and Deep Agents. All nine recorded cleanup actions passed with no cleanup failures.
Review notes
Sensitive path in NVIDIA/NemoClaw:
src/lib/onboard/host-gateway-process.test.ts. Self-review covers the complete test-only diff, the command-line lookup order, and neighboring fixtures. All nine hosted Advisor specialists are clear for this commit in run 35132304913. Their findings and E2E recommendations were read in full; the deterministic plan and every specialist select no additional live E2E for this fixture-only change. CodeRabbit skipped the draft; no CodeRabbit review or merge approval is claimed.Signed-off-by: Julie Yaunches jyaunches@nvidia.com
Summary by CodeRabbit