trifectatechfoundation / trifectatechfoundation/sudo-rs
Spurious failure of can_control_retry_delay_using_pam test
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
It seems to wait just a bit too little.
https://github.com/trifectatechfoundation/sudo-rs/actions/runs/17973829856/job/51122560538?pr=1279
---- sudo::password_retry::can_control_retry_delay_using_pam stdout ----
[sudo-compliance-tests/src/sudo/password_retry.rs:136:5] delta_millis = 2157
[sudo-compliance-tests/src/sudo/password_retry.rs:136:5] delta_millis = 2960
thread 'sudo::password_retry::can_control_retry_delay_using_pam' panicked at sudo-compliance-tests/src/sudo/password_retry.rs:196:5:
assertion failed: newer_delta_millis >= 3_100
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace
failures:
sudo::password_retry::can_control_retry_delay_using_pam
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 with sudo-compliance-tests/src/sudo/password_retry.rs, especially the can_control_retry_delay_using_pam test and its timing assertions around lines 136 and 196. Run this test and compare the measured delays with the reported 3,100 millisecond threshold; done means the test no longer fails spuriously under the relevant workflow conditions.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- testing-qa
- Issue type
- Bug
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Clearly specified
- Newbie friendliness
- 55/100