uutils / uutils/coreutils

test_terminate_child_on_receiving_terminate intermittent failure

Open
#11,870 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

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

Description

---- test_timeout::test_terminate_child_on_receiving_terminate stdout ----
bin: "/Users/runner/work/coreutils/coreutils/target/x86_64-apple-darwin/debug/coreutils"
run: /Users/runner/work/coreutils/coreutils/target/x86_64-apple-darwin/debug/coreutils timeout 10 sh -c trap 'echo child received TERM' TERM; sleep 5

thread 'test_timeout::test_terminate_child_on_receiving_terminate' panicked at tests/by-util/test_timeout.rs:229:10:
'' does not contain 'child received TERM'
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: uutests::util::CmdResult::stdout_contains
             at ./tests/uutests/src/lib/util.rs:768:9
   3: tests::test_timeout::test_terminate_child_on_receiving_terminate
             at ./tests/by-util/test_timeout.rs:224:5
   4: tests::test_timeout::test_terminate_child_on_receiving_terminate::{{closure}}
             at ./tests/by-util/test_timeout.rs:213:49
   5: core::ops::function::FnOnce::call_once
             at /rustc/6b00bc3880198600130e1cf62b8f8a93494488cc/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.

CICD / Build (macos-latest, x86_64-apple-darwin, feat_os_unix, true) (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 with tests/by-util/test_timeout.rs around test_terminate_child_on_receiving_terminate and the macOS CI failure linked in the issue. Reproduce the test on macOS, then inspect the timeout test's process and output expectations. Done means the intermittent failure is understood and the test passes reliably without losing the expected child output.

Written by the indexing model from the issue text.

Assessment

Tech stack
rust
Domain
cli, operating-systems, 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.