copy_buffer_does_not_touch_its_pages intermittent failure
Open
Nobody has claimed this yet.
U - dd
- Dominant language
- Rust
- Stars
- 24.1k
- Forks
- 2k
- Avg merge
- 1d 5h
- Merged PRs (30d)
- 365
Description
---- tests::copy_buffer_does_not_touch_its_pages stdout ----
thread 'tests::copy_buffer_does_not_touch_its_pages' panicked at src/uu/dd/src/dd.rs:1655:13:
attempt to subtract with overflow
stack backtrace:
0: __rustc::rust_begin_unwind
at /rustc/6b00bc3880198600130e1cf62b8f8a93494488cc/library/std/src/panicking.rs:697:5
1: core::panicking::panic_fmt
at /rustc/6b00bc3880198600130e1cf62b8f8a93494488cc/library/core/src/panicking.rs:75:14
2: core::panicking::panic_const::panic_const_sub_overflow
at /rustc/6b00bc3880198600130e1cf62b8f8a93494488cc/library/core/src/panicking.rs:175:17
3: uu_dd::tests::copy_buffer_does_not_touch_its_pages
at ./src/dd.rs:1655:13
4: uu_dd::tests::copy_buffer_does_not_touch_its_pages::{{closure}}
at ./src/dd.rs:1632:46
5: core::ops::function::FnOnce::call_once
at /rust/lib/rustlib/src/rust/library/core/src/ops/function.rs:250:5
6: core::ops::function::FnOnce::call_once
at /rustc/6b00bc3880198600130e1cf62b8f8a93494488cc/library/core/src/ops/function.rs:250:5
note: Some details are omitted, run with `RUST_BACKTRACE=full` for a verbose backtrace.
https://github.com/uutils/coreutils/actions/runs/33278279221/job/99171233811?pr=14242
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 copy_buffer_does_not_touch_its_pages test and inspect src/uu/dd/src/dd.rs around lines 1632 and 1655, where the backtrace identifies an overflowing subtraction. Reproduce the intermittent failure and trace the test inputs or page checks involved; done means the test passes reliably without the overflow panic.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- cli, testing-qa
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 55/100