uutils/coreutils

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

Open

#10097 opened on Jan 7, 2026

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

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

Tech stack
rust
Domain
testingperformance
Issue type
performance
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.
fresh
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
mostly clear
Prerequisites
basic Rusttest optimization concepts
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
60
Research direction
The issue lists specific test functions in coreutils::tests::test tail that take too long (up to 12s). Start by examining the test implementations in the repository, likely in `tests/` or similar directory. Look for common patterns like unnecessary sleeps, waits, or repeated setups. Consider using faster I/O or reducing timeouts. Check if the tests can be refactored to use mock file operations instead of real filesystem operations to speed them up. The goal is to bring each test under 1 second. Refer to the Codecov link for more details.