Michael BolinandGitHub b15c918836 fix: use cmd.exe in Windows unicode shell test (#16668) ...

## Why

This is a follow-up to #16665. The Windows `unicode_output` test should
still exercise a child process so it verifies PowerShell's UTF-8 output
configuration, but `$env:COMSPEC` depends on that environment variable
surviving the curated Bazel test environment.

Using `cmd.exe` keeps the child-process coverage while avoiding both
bare `cmd` + `PATHEXT` lookup and `$env:COMSPEC` env passthrough
assumptions.

## What

- Run `cmd.exe /c echo naïve_café` in the Windows branch of
`unicode_output`.

## Verification

- `cargo test -p codex-core unicode_output`

2026-04-03 00:32:08 -07:00

..

common

extract models manager and related ownership from core (#16508)

2026-04-02 23:00:02 -07:00

fixtures

Update tests to stop using sse_completed fixture (#10638)

2026-02-04 08:38:06 -08:00

suite

fix: use cmd.exe in Windows unicode shell test (#16668)

2026-04-03 00:32:08 -07:00

all.rs

extract models manager and related ownership from core (#16508)

2026-04-02 23:00:02 -07:00

cli_responses_fixture.sse

Add CLI streaming integration tests (#1542)

2025-07-12 18:05:58 -07:00

responses_headers.rs

core: remove cross-crate re-exports from lib.rs (#16512)

2026-04-01 23:06:24 -07:00