trifectatechfoundation / trifectatechfoundation/sudo-rs
Spurious failure of sudo::pass_auth::tty::correct_password
Open
Nobody has claimed this yet.
CI
test-framework
- Dominant language
- Rust
- Stars
- 4.5k
- Forks
- 179
- Avg merge
- 16h 45m
- Merged PRs (30d)
- 4
Description
I got this locally on https://github.com/trifectatechfoundation/sudo-rs/commit/37139a3b53d3ea3c3c407324313beba5f5936788:
---- sudo::pass_auth::tty::correct_password stdout ----
thread 'sudo::pass_auth::tty::correct_password' (1319995) panicked at sudo-compliance-tests/src/sudo/pass_auth/tty.rs:17:10:
program failed with exit status: 5
stdout:
stderr:
stack backtrace:
0: __rustc::rust_begin_unwind
at /rustc/ed61e7d7e242494fb7057f2657300d9e77bb4fcb/library/std/src/panicking.rs:698:5
1: core::panicking::panic_fmt
at /rustc/ed61e7d7e242494fb7057f2657300d9e77bb4fcb/library/core/src/panicking.rs:75:14
2: sudo_test::docker::command::Output::assert_success
at /home/bjorn/Projects/sudo-rs/test-framework/sudo-test/src/docker/command.rs:167:13
3: sudo_compliance_tests::sudo::pass_auth::tty::correct_password
at ./src/sudo/pass_auth/tty.rs:17:10
4: sudo_compliance_tests::sudo::pass_auth::tty::correct_password::{{closure}}
at ./src/sudo/pass_auth/tty.rs:8:22
5: core::ops::function::FnOnce::call_once
at /home/bjorn/.rustup/toolchains/stable-x86_64-unknown-linux-gnu/lib/rustlib/src/rust/library/core/src/ops/function.rs:250:5
6: core::ops::function::FnOnce::call_once
at /rustc/ed61e7d7e242494fb7057f2657300d9e77bb4fcb/library/core/src/ops/function.rs:250:5
note: Some details are omitted, run with `RUST_BACKTRACE=full` for a verbose backtrace.
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
Reproduce sudo::pass_auth::tty::correct_password from sudo-compliance-tests/src/sudo/pass_auth/tty.rs at commit 37139a3b53d3ea3c3c407324313beba5f5936788, then inspect the failure reported by test-framework/sudo-test/src/docker/command.rs. Compare the test setup and command output to determine why it exits with status 5; done means the compliance test passes reliably without masking failures.
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
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100