test_ls::test_ls_color_norm failure
Open
Nobody has claimed this yet.
U - ls
- Dominant language
- Rust
- Stars
- 24.1k
- Forks
- 2k
- Avg merge
- 1d 5h
- Merged PRs (30d)
- 365
Description
failures:
---- test_ls::test_ls_color_norm stdout ----
bin: "/home/mathieu/Code/uutils-coreutils/target/debug/coreutils"
touch: /tmp/.tmp0Y7AlY/exe
touch: /tmp/.tmp0Y7AlY/no_color
run: /home/mathieu/Code/uutils-coreutils/target/debug/coreutils ls -gGU --color exe no_color
thread 'test_ls::test_ls_color_norm' panicked at tests/by-util/test_ls.rs:5786:10:
'norm exe
norm no_color
' does not contain 'norm exe
norm no_color'
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace
failures:
test_ls::test_ls_color_norm
test result: FAILED. 3683 passed; 1 failed; 34 ignored; 0 measured; 0 filtered out; finished in 15.36s
System information:
Fedora 42
Linux sophia 6.16.8-200.fc42.x86_64 #1 SMP PREEMPT_DYNAMIC Fri Sep 19 17:47:18 UTC 2025 x86_64 GNU/Linux
zsh
ghostty, but also occurs with other terminals
rustc 1.90.0 (1159e78c4 2025-09-14)
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by running the failing test test_ls::test_ls_color_norm and inspect tests/by-util/test_ls.rs around line 5786. Reproduce the reported ls -gGU --color invocation on the provided environment, then trace the observed output versus the assertion. Done means the failure is resolved and the test passes.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- cli
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100