uutils / uutils/coreutils

test_cp_recursive_dir_drops_setuid_setgid is failing

Closed
#14,697 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

U - cp
Dominant language
Rust
Stars
24.1k
Forks
2k
Avg merge
1d 5h
Merged PRs (30d)
365

Description

---- test_cp::test_cp_recursive_dir_drops_setuid_setgid stdout ----
bin: "/home/runner/work/coreutils/coreutils/target/wasm32-wasip1/debug/coreutils.wasm"
mkdir: /tmp/.tmpE3Tn7n/tree
mkdir: /tmp/.tmpE3Tn7n/tree/setgid
mkdir: /tmp/.tmpE3Tn7n/tree/setuid
mkdir: /tmp/.tmpE3Tn7n/tree/sticky
run: /home/runner/work/coreutils/coreutils/target/wasm32-wasip1/debug/coreutils.wasm cp -r tree plain

thread 'test_cp::test_cp_recursive_dir_drops_setuid_setgid' (20481) panicked at tests/by-util/test_cp.rs:1099:5:
assertion `left == right` failed
  left: 489
 right: 457
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace

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.

Research direction

Start with tests/by-util/test_cp.rs:1099 and reproduce test_cp::test_cp_recursive_dir_drops_setuid_setgid for the wasm32-wasip1 target. Compare the reported mode values with the test's expected behavior and trace the cp implementation involved; done means the test passes without weakening its setuid/setgid assertion.

Written by the indexing model from the issue text.

Assessment

Tech stack
rust, wasm
Domain
cli, testing
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Active
Clarity
Needs clarification
Newbie friendliness
48/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.