reduce test execution: coreutils::tests::test_tail::*
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 24.1k
- Forks
- 2k
- Avg merge
- 1d 5h
- Merged PRs (30d)
- 365
Description
it is currently 12.030s for the longest
see https://app.codecov.io/gh/uutils/coreutils/tests
see:
coreutils::tests::test_tail::test_follow_name_move_retry2 12.030s
coreutils::tests::test_tail::test_follow_descriptor_vs_rename1 12.029s
coreutils::tests::test_tail::test_retry7 10.030s
coreutils::tests::test_tail::test_follow_name_move_retry1 10.029s
coreutils::tests::test_tail::test_follow_name_move2 8.029s
coreutils::tests::test_tail::test_follow_name_move_create2 8.029s
coreutils::tests::test_tail::test_retry4 8.029s
coreutils::tests::test_tail::test_follow_name_multiple 7.541s
coreutils::tests::test_tail::test_retry9 7.018s
coreutils::tests::test_tail::test_follow_descriptor_vs_rename2 6.029s
coreutils::tests::test_tail::test_follow_name_retry_headers 6.029s
Ideally, they should take less a second
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 with the coreutils::tests::test_tail tests named in the issue and use the linked Codecov test timings to identify the slow paths. Determine why the follow, retry, and rename cases take several seconds, then verify that their behavior remains covered while reducing the listed test durations to under a second.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- cli, performance, testing
- Issue type
- Refactor
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 55/100