trifectatechfoundation / trifectatechfoundation/sudo-rs

Spurious failure of sudo::syslog::sudo_logs_every_executed_command

Open
#1,371 0 comments 0 reactions 0 assignees View on GitHub

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::syslog::sudo_logs_every_executed_command stdout ----

thread 'sudo::syslog::sudo_logs_every_executed_command' (1446518) panicked at sudo-compliance-tests/src/sudo/syslog.rs:19:5:
"" did not contain "COMMAND=/usr/bin/true"
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_compliance_tests::sudo::syslog::sudo_logs_every_executed_command
             at ./src/macros.rs:6:9
   3: sudo_compliance_tests::sudo::syslog::sudo_logs_every_executed_command::{{closure}}
             at ./src/sudo/syslog.rs:6:38
   4: 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
   5: 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

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 sudo-compliance-tests/src/sudo/syslog.rs, especially sudo_logs_every_executed_command, and reproduce the failure at the reported commit. Inspect why the captured output is empty instead of containing COMMAND=/usr/bin/true; done means the test reliably observes the expected syslog entry or the underlying failure is documented with a reproducible explanation.

Written by the indexing model from the issue text.

Assessment

Tech stack
rust
Domain
operating-systems, testing-qa
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.