Windows: status helper tests expect tilde-shortened AppData path

Open Beginner friendly
#19,623 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
75/100
Issue type
Bug
Clarity
Clearly specified
Activity status
Quiet
Tech stack
rust
Domain
cli, testing-qa

Research direction

Run RUST_MIN_STACK=16777216 cargo test -p codex-tui on Windows and inspect the three named status::helpers::*compose_agents_summary* tests. Compare their expected paths with the observed Windows output, then verify the affected assertions pass without changing the unrelated stack-overflow workaround.

Written by the indexing model from the issue text.

Description

bug windows-os

Summary

On Windows, cargo test -p codex-tui can fail three status::helpers::*compose_agents_summary* tests because the expected path uses ~\AppData\... while the actual output uses the expanded home path C:\Users\<user>\AppData\....

This surfaced after working around the separate stack-overflow issue in #19596 with RUST_MIN_STACK=16777216.

Repro

On Windows PowerShell / Git Bash environment:

$env:RUST_MIN_STACK='16777216'
cargo test -p codex-tui

Failing tests

  • status::helpers::tests::compose_agents_summary_includes_global_agents_path
  • status::helpers::tests::compose_agents_summary_names_global_agents_override
  • status::helpers::tests::compose_agents_summary_orders_global_before_project_agents

Observed diff shape

Expected:

~\AppData\Local\Temp\...\AGENTS.md

Actual:

C:\Users\stefa\AppData\Local\Temp\...\AGENTS.md

For compose_agents_summary_orders_global_before_project_agents, the same mismatch appears inside Some(...).

Notes

This appears independent from the stack-overflow abort tracked in #19596. With the stack increased, the suite gets far enough to expose these normal assertion failures.

Dominant language
Rust
Stars
125k
Forks
19.5k
Avg merge
1m
Merged PRs (30d)
1k

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from openai/codex

All issues in openai/codex

Similar issues

More Rust issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.