GnuTests: Do not build GNU coreutils for faster CI

[oech3]

~conifgure is too long. I want to DL "non-patched" prebuilt GNU coreutils for faster CI.~

[pixelb]

Note you can pass a stored config.cache file to configure ith the -C option, which greatly speeds up operations

[oech3]

I think CI is always clean build. BTW, is it really needed to build GNU coreutils on CI to run GNU tests with uutils?

(Hosting config.cache on this repo might still good idea)

[oech3]

https://github.com/uutils/coreutils/issues/9331#issuecomment-3553495114

Without make, I could not run GNU tests. Is running tests without building GNU coreutils not supported (yet)?

[pixelb]

Fundamentally you shouldn't need to build before using the tests against uutils. A ./configure run would be advised though as some tests inspect lib/config.h. What errors are you seeing?

[oech3]

Using GNU test suite without building coreutils might useful also for *box, *BSD coreutils, vlang-coreutils and distro patched GNU coreutils. It it fine to move this issue to GNU's repo?

[oech3]

I think uutils cannot do that for portability, but can I simply host getlimits > getlimits.txt and put a cat getlimits.txt wrapper?

[oech3]

Or --enable-no-install-program=VERYVERYLONGSTRING? I think uu's test suite is forgotting to build GNU arch command, but test for arch is running since uutils always build arch.

[Edit]--enable-install-program="arch" added 2 failing tests too uutil's test suite wrapper...

[oech3]

@sylvestre One of a idea to stop building every GNU at CI is cloning GNU's repository and releaseing prebuilt of test suite, and fetch it at here. Such scripts should be still MIT...?

[oech3]

(Also people want to DL prebuilt GNU coreutils for benchmark).

[oech3]

By caching config.cache only: https://github.com/uutils/coreutils/pull/9627#issuecomment-3636638477

I'll actions/cache@vN getlimits binary too.