uutils / uutils/coreutils

test_env_arg_ignore_signal_valid_signals intermittent failure

Open
#11,772 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

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

Description

---- test_env::test_env_arg_ignore_signal_valid_signals stdout ----
bin: "/Users/runner/work/coreutils/coreutils/target/debug/coreutils"
run: /Users/runner/work/coreutils/coreutils/target/debug/coreutils env --ignore-signal=int sleep 1000
bin: "/Users/runner/work/coreutils/coreutils/target/debug/coreutils"
run: /Users/runner/work/coreutils/coreutils/target/debug/coreutils env --ignore-signal=usr2 sleep 1000
bin: "/Users/runner/work/coreutils/coreutils/target/debug/coreutils"
run: /Users/runner/work/coreutils/coreutils/target/debug/coreutils env --ignore-signal=int,usr2 sleep 1000

thread 'test_env::test_env_arg_ignore_signal_valid_signals' (101074) panicked at tests/by-util/test_env.rs:897:9:
assertion failed: !target.is_alive()
stack backtrace:
   0: __rustc::rust_begin_unwind
             at /rustc/e408947bfd200af42db322daf0fadfe7e26d3bd1/library/std/src/panicking.rs:689:5
   1: core::panicking::panic_fmt
             at /rustc/e408947bfd200af42db322daf0fadfe7e26d3bd1/library/core/src/panicking.rs:80:14
   2: core::panicking::panic
             at /rustc/e408947bfd200af42db322daf0fadfe7e26d3bd1/library/core/src/panicking.rs:150:5
   3: tests::test_env::test_env_arg_ignore_signal_valid_signals
             at ./tests/by-util/test_env.rs:897:9
   4: tests::test_env::test_env_arg_ignore_signal_valid_signals::{{closure}}
             at ./tests/by-util/test_env.rs:883:46
   5: core::ops::function::FnOnce::call_once
             at /rustc/e408947bfd200af42db322daf0fadfe7e26d3bd1/library/core/src/ops/function.rs:250:5
   6: core::ops::function::FnOnce::call_once
             at /rustc/e408947bfd200af42db322daf0fadfe7e26d3bd1/library/core/src/ops/function.rs:250:5
note: Some details are omitted, run with `RUST_BACKTRACE=full` for a verbose backtrace.

L10n (Localization) / L10n/Build and Test (macos-latest, feat_os_unix) (pull_request)

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 in tests/by-util/test_env.rs around test_env_arg_ignore_signal_valid_signals, especially lines 883-897, and run the targeted test on macOS. Investigate why the sleep process remains alive after the env --ignore-signal cases. Done means the intermittent failure is understood and the test passes reliably.

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
Quiet
Clarity
Mostly clear
Newbie friendliness
48/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.