"GNU testsuite comparison" don't take into account the ignore intermittent list
Open
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 24.1k
- Forks
- 2k
- Avg merge
- 1d 5h
- Merged PRs (30d)
- 365
Description
GNU testsuite comparison:
Congrats! The gnu test misc/stdbuf.log is no longer failing!
Congrats! The gnu test timeout/timeout.log is no longer failing!
Example: https://github.com/uutils/coreutils/issues/7495#issuecomment-2738497130
It is clearly my fault with recent changes
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
Inspect the GNU testsuite comparison and its ignore-intermittent list, using the linked issue comment and the reported misc/stdbuf.log and timeout/timeout.log examples as starting points. Reproduce the comparison and ensure ignored intermittent results are not reported as newly passing or failing.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- testing
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100