test(installer): make ACP shim race deterministic - #11523
Conversation
Signed-off-by: Charan Jagwani <cjagwani@nvidia.com>
|
Important Review skippedAuto reviews are disabled on base/target branches other than the default branch. Please check the settings in the CodeRabbit UI or the ⚙️ Run configurationConfiguration used: Path: .coderabbit.yaml Review profile: CHILL Plan: Enterprise Run ID: You can disable this status message by setting the Use the checkbox below for a quick retry:
Comment |
Code Coverage OverviewLanguages: TypeScript TypeScript / code-coverage/pluginThe overall line coverage in commit 600375b in the TypeScript / code-coverage/cliThe overall line coverage in commit 600375b in the Show a line coverage summary of the most impacted files.
Updated |
Outcome
The ACP shim replacement-race test now deterministically exercises the intended identity-change path instead of occasionally observing a reused inode and accepting a different safe failure path.
Reason
PR #11458's Linux CLI shard failed because the test removed the original shim before creating its replacement. The filesystem could reuse the deleted inode, causing the installer to report that the shim was no longer managed instead of reporting an identity change. Both outcomes fail closed, but the fixture asserted only the identity-change diagnostic.
Related issues
Part of #11458.
Changes
Verification
npx vitest run --project integration test/install/install-npm-resolution.test.ts --coverage=false— 29/29 tests passed.npx oxfmt --check test/install/install-npm-resolution.test.ts— passed.npx oxlint test/install/install-npm-resolution.test.ts— passed.node --max-old-space-size=8192 node_modules/typescript/bin/tsc -p tsconfig.cli.json --incremental— passed after building the repository's CLI and plugin artifacts.Review notes
This PR intentionally targets
codex/10947-acp-review-repairs, the source branch of #11458, and contains only the test-fixture correction for its failing CLI shard. No production or user-facing behavior changes, so no documentation update is needed.Signed-off-by: Charan Jagwani cjagwani@nvidia.com