Dino Test fails from Codex, but runs perfectly on Windows powershell

What version of the Codex App are you using (From “About Codex” dialog)?

26.519.41501

What subscription do you have?

Pro

What platform is your computer?

Microsoft Windows NT 10.0.26200.0 x64

What issue are you seeing?

I always receive this error in codex run when codex is trying to run Dino test

The full Deno test command still hits the known Windows Deno pipe panic after type-checking the test files, so it didn’t complete. I’m narrowing to the unlock tests and a resolver dry run to separate actual failures from the runner issue.
Here is codex reply

I reproduced it. The failure is with Deno test, not the resolver code itself.
Failing path:
package.json (line 15) runs deno test supabase/functions/_shared/*.test.ts
Local Deno is deno 2.8.0, installed at C:\Users\coron\AppData\Local\Microsoft\WinGet\Packages\DenoLand.Deno_Microsoft.Winget.Source_8wekyb3d8bbwe\deno.exe
On Windows, deno test panics before running assertions:
text

*** Unexpected client pipe failure "\.\pipe\deno_pipe_...": 5

Deno has panicked. This is a bug in Deno.

Platform: windows x86_64
Version: 2.8.0
panicked at cli\tools\test\channel.rs:252:49:
called Result::unwrap() on an Err value:
Os { code: 6, message: "The handle is invalid." }

I confirmed it is not caused by EmojiWar test code:
deno test supabase/functions/_shared/interaction-matrix.test.ts also panics.
deno test supabase/functions/_shared/battle-simulator.test.ts also panics.
A disposable one-line test, Deno.test("smoke", () => {});, also panicked the same way.
deno check succeeds on the same files.
deno run supabase/functions/_shared/verify-resolver.ts succeeds.
npm run verify:resolver passes all 18/18 resolver checks.
So the reason it fails for me is: Deno 2.8.0 on Windows is crashing inside its test-runner IPC/channel code, likely around named pipe handling. It is not a TypeScript error, not a failing assertion, and not a resolver logic problem.

What steps can reproduce the bug?

Feedback ID: 019e5644-4846-7661-ac22-0ba26c04bb03

What is the expected behavior?

_No response_

Additional information

_No response_