uutils/coreutils

reduce test execution: coreutils::tests::test_tail::*

Open

#10,097 opened on Jan 7, 2026

View on GitHub
 (2 comments) (0 reactions) (0 assignees)Rust (1,852 forks)batch import
U - tailgood first issue

Repository metrics

Stars
 (23,246 stars)
PR merge metrics
 (Avg merge 5d 23h) (239 merged PRs in 30d)

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

Research direction
Identify the slowest subsets of the test tail tests by analyzing the test durations. Look for repeated setup code or unnecessary delays (e.g., sleep calls) and try to consolidate tests or reduce wait times. Consider using tempfile helpers or mocking to speed up file operations.
Tech stack
rust
Domain
testing
Issue type
Test
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
Half day
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
RustGit
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
70