Michael Bolin 14f95db57b fix: use COMSPEC in Windows unicode shell test (#16665) ...

## Why

Windows Bazel shell tests launch PowerShell with a curated environment,
so `PATHEXT` may be absent. The existing `unicode_output` test invokes
bare `cmd`, which can fail before the test exercises UTF-8 child-process
output.

## What

- Use `$env:COMSPEC /c echo naïve_café` in the Windows branch of
`unicode_output`.
- Preserve the external child-process path instead of switching the test
to a PowerShell builtin.

## Verification

- `cargo test -p codex-core unicode_output`

14f95db57b · 2026-04-02 23:54:02 -07:00

History

..

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 COMSPEC in Windows unicode shell test (#16665)

2026-04-02 23:54:02 -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