Android CI: `test_test::test_file_N` 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
test_file_N often fails on Android CI.
One example: https://github.com/uutils/coreutils/actions/runs/14053822619/job/39348967416
[2025-03-25 07:37:52] TRY 3 FAIL [ 0.070s] coreutils::tests test_test::test_file_N
[2025-03-25 07:37:52] ──── TRY 3 STDOUT: coreutils::tests test_test::test_file_N
[2025-03-25 07:37:52]
[2025-03-25 07:37:52] running 1 test
[2025-03-25 07:37:52] run: /data/data/com.termux/files/home/coreutils/target/debug/coreutils test -N file
[2025-03-25 07:37:52] touch: /data/data/com.termux/files/usr/tmp/.tmpobxyW9/file
[2025-03-25 07:37:52] run: /data/data/com.termux/files/home/coreutils/target/debug/coreutils test -N file
[2025-03-25 07:37:52] test test_test::test_file_N ... FAILED
[2025-03-25 07:37:52]
[2025-03-25 07:37:52] failures:
[2025-03-25 07:37:52]
[2025-03-25 07:37:52] failures:
[2025-03-25 07:37:52] test_test::test_file_N
[2025-03-25 07:37:52]
[2025-03-25 07:37:52] test result: FAILED. 0 passed; 1 failed; 0 ignored; 0 measured; 3633 filtered out; finished in 0.06s
[2025-03-25 07:37:52]
[2025-03-25 07:37:52] ──── TRY 3 STDERR: coreutils::tests test_test::test_file_N
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 test_test::test_file_N and reproduce it in the Android CI run linked in the issue. Read the test output around coreutils test -N file and compare repeated attempts. Done means the test no longer flakes on Android CI and passes reliably.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- android, github-actions, rust
- Domain
- ci-cd, cli, testing-qa
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 38/100