uutils / uutils/coreutils

test_create_one_fifo_with_non_file_permission_mode intermittent failure

Open
#11,762 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"
    run: /home/runner/work/coreutils/coreutils/target/debug/coreutils mkfifo abcd -m 1777
    test test_mkfifo::test_create_one_fifo_with_non_file_permission_mode ... FAILED

    failures:

    ---- test_mkfifo::test_create_one_fifo_with_non_file_permission_mode stdout ----
    ---- test_mkfifo::test_create_one_fifo_with_non_file_permission_mode stderr ----


    failures:
        test_mkfifo::test_create_one_fifo_with_non_file_permission_mode

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

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

    Diff < left / right > :
     mkfifo: mode must specify only file permission bits
    <LLVM Profile Error: Failed to write file "/home/runner/work/coreutils/coreutils/coverage/traces/coverage-6931721886030836390_0.profraw": Permission denied

https://github.com/uutils/coreutils/actions/runs/24285074447/job/70912994688?pr=11759

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 the failing assertion and reproduce the mkfifo command from the linked GitHub Actions job. Investigate the intermittent LLVM profile permission error and make the test run reliably, then verify the targeted test passes in the affected CI configuration.

Written by the indexing model from the issue text.

Assessment

Tech stack
github-actions, rust
Domain
ci-cd, cli, testing-qa
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.