[xtqqczze]

Closes #14914.
Relates to #14664.

Required to compile uutests and enables the fd_soft_limit code path in uu_sort for Redox targets.

[sylvestre]

sorry but i am not going to revert anything until we have a CI running for redox

[oech3]

I think we don't need to revert this since we were not running test(impossible?) for Redox on the CI previously.

[xtqqczze]

I think we should add a check-only job at the very least:

cargo check --all-targets --features feat_os_unix_redox --target x86_64-unknown-redox

We can set continue-on-error: true for now so that any existing errors don’t block CI, while still giving us visibility into Redox build issues.

[sylvestre]

Sounds good

[oech3]

Do we really need to hurry supporting test on redox? Most logic are shared with other platforms.

[codspeed]

Merging this PR will not alter performance

1 warning, 1 note

⚠️ 120 benchmarks are dominated by system calls

System calls cannot be simulated consistently and are left out of the measure. The reported value understates the real cost. Switch to the Walltime instrument to measure them.

Learn more about system calls

See affected benchmarks

ℹ️ 1 benchmark has no flamegraph

The flamegraph wasn't generated: most of the time was spent in runtime internals, which would leave nothing useful to analyze.

See affected benchmarks

✅ 401 untouched benchmarks
⏩ 70 skipped benchmarks¹

---

_{Comparing xtqqczze:GH14664 (c415bfc) with main (18bc31f)}

Footnotes

1. 70 benchmarks were skipped, so the baseline results were used instead. If they were deleted from the codebase, click here and archive them to remove them from the performance reports. ↩

[oech3]

If we replaced rustix with rlimit, we need large diff again to remove it after rustix supported rlimit on redox.

[xtqqczze]

Split the uutests changes to #14252.

[xtqqczze]

If we replaced rustix with rlimit, we need large diff again to remove it after rustix supported rlimit on redox.

rustix doesn't seem to be actively maintained. Perhaps we should consider forking it.

[oech3]

Is there any collaborator for rustix repo in ? We should consider asking maintainer to add collaborator from bytecodealliance.

[oech3]

Since their famous project (e.g. wasmtime) depends on rustix, I think they cannot abandon it.

[sylvestre]

Thanks for your PR