uutils / uutils/coreutils

test_mkfifo_permission_unchanged_when_failed intermittent failure

Open
#11,736 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

    running 1 test
    bin: "/home/runner/work/coreutils/coreutils/target/debug/coreutils"
    write(default): /tmp/.tmpzfXtl5/test_file
    run: /home/runner/work/coreutils/coreutils/target/debug/coreutils mkfifo test_file -m 666
    test test_mkfifo::test_mkfifo_permission_unchanged_when_failed ... FAILED

    failures:

    ---- test_mkfifo::test_mkfifo_permission_unchanged_when_failed stdout ----
    ---- test_mkfifo::test_mkfifo_permission_unchanged_when_failed stderr ----


    failures:
        test_mkfifo::test_mkfifo_permission_unchanged_when_failed

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

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

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

https://github.com/uutils/coreutils/actions/runs/24202125863/job/70648306358

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 at line 236 and reproduce test_mkfifo::test_mkfifo_permission_unchanged_when_failed using the mkfifo command shown in the log. Compare the intermittent failure with the linked GitHub Actions run, including the LLVM Profile Error, and confirm the test completes reliably with the expected failure output.

Written by the indexing model from the issue text.

Assessment

Tech stack
rust
Domain
cli, testing
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Quiet
Clarity
Needs clarification
Newbie friendliness
48/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.