Skip a unit test that is using a bash script on Windows#1490
Skip a unit test that is using a bash script on Windows#1490juliusmarminge merged 1 commit intopingdotgg:mainfrom
Conversation
|
Important Review skippedAuto reviews are disabled on this repository. Please check the settings in the CodeRabbit UI or the ⚙️ Run configurationConfiguration used: Repository UI Review profile: CHILL Plan: Pro Run ID: You can disable this status message by setting the Use the checkbox below for a quick retry:
✨ Finishing Touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
There was a problem hiding this comment.
Cursor Bugbot has reviewed your changes and found 1 potential issue.
Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, enable autofix in the Cursor dashboard.
05ef01c to
af5b0b0
Compare

What Changed
Skip PATH inheritance unit test on Windows
Why
It's using a bash script and that won't work on win32
Checklist
Note
Low Risk
Low risk: only changes test execution by skipping a bash-script-based unit test on Windows, with no production code impact.
Overview
Updates
ProviderRegistry.test.tsto skip on Windows thecheckCodexProviderStatusPATH-inheritance test that writes/executes a#!/bin/shmockcodexbinary, preventing win32 CI failures while keeping the test behavior unchanged on non-Windows platforms.Written by Cursor Bugbot for commit af5b0b0. This will update automatically on new commits. Configure here.
Note
Skip bash-dependent
checkCodexProviderStatustest on WindowsThe test
"inherits PATH when launching the codex probe with a CODEX_HOME override"in ProviderRegistry.test.ts uses a bash script incompatible with Windows. Replacesit.effect(...)withit.effect.skipIf(process.platform === "win32")(...)to skip execution on Windows while leaving the test body unchanged.Macroscope summarized af5b0b0.