test_split::test_round_robin_limited_file_descriptors fails sporadically on x86_64-unknown-linux-musl #6031
Description
Example failure:
failures:
---- test_split::test_round_robin_limited_file_descriptors stdout ----
run: /target/x86_64-unknown-linux-musl/debug/coreutils split -n r/40 onehundredlines.txt
thread 'test_split::test_round_robin_limited_file_descriptors' panicked at 'Command was expected to succeed. code: 1
stdout =
stderr = split: unable to open 'xbj'; aborting
', tests/by-util/test_split.rs:1646:10
stack backtrace:
0: rust_begin_unwind
at /rustc/90c541806f23a127002de5b4038be731ba1458ca/library/std/src/panicking.rs:578:5
1: core::panicking::panic_fmt
at /rustc/90c541806f23a127002de5b4038be731ba1458ca/library/core/src/panicking.rs:67:14
2: tests::common::util::CmdResult::success
at ./tests/common/util.rs:400:9
3: tests::common::util::UCommand::succeeds
at ./tests/common/util.rs:1599:9
4: tests::test_split::test_round_robin_limited_file_descriptors
at ./tests/by-util/test_split.rs:1643:5
5: tests::test_split::test_round_robin_limited_file_descriptors::{{closure}}
at ./tests/by-util/test_split.rs:1642:48
6: core::ops::function::FnOnce::call_once
at /rustc/90c541806f23a127002de5b4038be731ba1458ca/library/core/src/ops/function.rs:250:5
7: core::ops::function::FnOnce::call_once
at /rustc/90c541806f23a127002de5b4038be731ba1458ca/library/core/src/ops/function.rs:250:5
note: Some details are omitted, run with `RUST_BACKTRACE=full` for a verbose backtrace.
failures:
test_split::test_round_robin_limited_file_descriptors
As far as my analyses is correct, the filename contains also the chunk number as its automatically generated:
xaa - 1
xab - 2
xac - 3
...
xaz - 26
xba - 27
...
xbj - 36
So it seems like the limited fd handling works in general as otherwise it would not be able to generate 36 files, but only 9.
I'm currently trying to fix the issue just by making the handling of the fd limitation more robust.
Other example links:
https://github.com/cre4ture/coreutils/actions/runs/8103387718/job/22147977331?pr=9
Here it was 100% successfull despite 12500 runs, but it was executed as single test only.
Probably the missing background-load caused stability.
https://github.com/cre4ture/coreutils/actions/runs/8122922623/job/22202872494?pr=9