uutils / uutils/coreutils

test_create_one_fifo_already_exists intermittent failure

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

Nobody has claimed this yet.

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

Description

    bin: "/home/runner/work/coreutils/coreutils/target/debug/coreutils"
    run: /home/runner/work/coreutils/coreutils/target/debug/coreutils mkfifo abcdef abcdef
    test test_mkfifo::test_create_one_fifo_already_exists ... FAILED

    failures:

    ---- test_mkfifo::test_create_one_fifo_already_exists stdout ----
    ---- test_mkfifo::test_create_one_fifo_already_exists stderr ----


    failures:
        test_mkfifo::test_create_one_fifo_already_exists

    test result: FAILED. 0 passed; 1 failed; 0 ignored; 0 measured; 5135 filtered out; finished in 0.19s
    
  stderr ───

    thread 'main' (37702) panicked at tests/by-util/test_mkfifo.rs:83:10:
    assertion failed: `(left == right)`

    Diff < left / right > :
     mkfifo: cannot create fifo 'abcdef': File exists
    <LLVM Profile Error: Failed to write file "/home/runner/work/coreutils/coreutils/coverage/traces/coverage-9324049985853773752_2.profraw": Permission denied
     


    note: run with `RUST_BACKTRACE=1` environment variable to display a 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 tests/by-util/test_mkfifo.rs, especially test_mkfifo::test_create_one_fifo_already_exists and the assertion at line 83. Reproduce the reported command and inspect the expected stderr alongside the LLVM Profile Error; done means the intermittent test 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
52/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.