ci: Switch back to default coreutils (uutils) after libffi-sys bump

[Zalathar]

Now that Miri has updated to the latest libffi-sys, we should be able to remove the GNU coreutils workaround, and switch back to the default coreutils (uutils) in the runners using Ubuntu 25.10 images.

If we encounter any other uutils compatibility problems in the future, they should hopefully be easier to trace back to specific changes.

• ci: Use GNU coreutils to work around a libffi-sys build failure #147581
• native-lib: bump libffi miri#4634
• miri subtree update #147744

Closes #147556.

[rustbot]

r? @marcoieni

rustbot has assigned @marcoieni.
They will have a look at your PR within the next two weeks and either review your PR or reassign to another reviewer.

Use r? to explicitly pick a reviewer

[Zalathar]

@bors try jobs=aarch64-gnu,aarch64-gnu-debug,aarch64-gnu-llvm-20-1,aarch64-gnu-llvm-20-2

[rust-bors]

☀️ Try build successful (CI)
Build commit: 95ae112 (95ae112fedd15ff1568041486223bb6c5d15fb54, parent: 53a741fc4b8cf2d8e7b1b2336ed8edf889db84f4)

[jieyouxu]

r? jieyouxu

[jieyouxu]

Thanks

View changes since this review

[jieyouxu]

@bors r+ rollup=never

[bors]

📌 Commit 439431a has been approved by jieyouxu

It is now in the queue for this repository.

[bors]

⌛ Testing commit 439431a with merge 843f8ce...

[bors]

☀️ Test successful - checks-actions
Approved by: jieyouxu
Pushing 843f8ce to master...

[github-actions]

What is this?

This is an experimental post-merge analysis report that shows differences in test outcomes between the merged PR and its parent PR.

Comparing 9606412 (parent) -> 843f8ce (this PR)

Test differences

Show 2 test diffs

2 doctest diffs were found. These are ignored, as they are noisy.

Test dashboard

Run

cargo run --manifest-path src/ci/citool/Cargo.toml -- \
    test-dashboard 843f8ce2ebc01d35a30484eadc8a84cdc6130844 --output-dir test-dashboard

And then open test-dashboard/index.html in your browser to see an overview of all executed tests.

Job duration changes

1. dist-aarch64-apple: 5563.0s -> 7815.0s (+40.5%)
2. dist-x86_64-apple: 6723.0s -> 8954.3s (+33.2%)
3. pr-check-1: 1319.5s -> 1633.1s (+23.8%)
4. pr-check-2: 2141.7s -> 2574.1s (+20.2%)
5. x86_64-gnu-llvm-21-3: 5617.6s -> 6567.2s (+16.9%)
6. x86_64-gnu-aux: 6012.5s -> 7011.2s (+16.6%)
7. dist-various-1: 3879.1s -> 4492.5s (+15.8%)
8. tidy: 173.3s -> 195.4s (+12.7%)
9. dist-apple-various: 3644.7s -> 4027.0s (+10.5%)
10. i686-gnu-1: 7041.6s -> 7678.0s (+9.0%)

How to interpret the job duration changes?

Job durations can vary a lot, based on the actual runner instance
that executed the job, system noise, invalidated caches, etc. The table above is provided
mostly for t-infra members, for simpler debugging of potential CI slow-downs.

[rust-timer]

Finished benchmarking commit (843f8ce): comparison URL.

Overall result: no relevant changes - no action needed

@rustbot label: -perf-regression

Instruction count

This benchmark run did not return any relevant results for this metric.

Max RSS (memory usage)

This benchmark run did not return any relevant results for this metric.

Cycles

Results (secondary 0.5%)

A less reliable metric. May be of interest, but not used to determine the overall result above.

	mean	range	count
Regressions ❌ (primary)	-	-	0
Regressions ❌ (secondary)	4.5%	[4.5%, 4.5%]	1
Improvements ✅ (primary)	-	-	0
Improvements ✅ (secondary)	-3.4%	[-3.4%, -3.4%]	1
All ❌✅ (primary)	-	-	0

Binary size

This benchmark run did not return any relevant results for this metric.

Bootstrap: 473.265s -> 483.325s (2.13%)
Artifact size: 390.81 MiB -> 390.81 MiB (-0.00%)