CI: GNU test "timeout" is flaky
Open
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 24.1k
- Forks
- 2k
- Avg merge
- 1d 5h
- Merged PRs (30d)
- 365
Description
GNU test failed: tests/timeout/timeout. tests/timeout/timeout is passing on 'main'. Maybe you have to rebase?
This false positive plagues many PRs and causes CI to be red quite often. Recent examples:
- https://github.com/uutils/coreutils/pull/6719#issuecomment-2364556796
- https://github.com/uutils/coreutils/pull/6720#issuecomment-2364717134
- https://github.com/uutils/coreutils/pull/6725#issuecomment-2365211679
- https://github.com/uutils/coreutils/pull/6731#issuecomment-2369887950
And many more. Can we drop that GNU test? What do you think?
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by locating the CI configuration that runs the GNU test for tests/timeout/timeout, then review the linked failures and compare behavior on main. Reproduce the false positive if possible and determine whether removing that test stops the recurring red CI results without losing required coverage.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- ci-cd, testing
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100