*bsd.yml: boost CI

[oech3]

obsd: about -2 min?

[github-actions]

GNU testsuite comparison:

Skip an intermittent issue tests/shuf/shuf-reservoir (fails in this run but passes in the 'main' branch)
Skip an intermittent issue tests/sort/sort-stale-thread-mem (fails in this run but passes in the 'main' branch)
Skip an intermittent issue tests/tail/inotify-dir-recreate (fails in this run but passes in the 'main' branch)

[github-actions]

GNU testsuite comparison:

Congrats! The gnu test tests/seq/seq-epipe is now passing!

[github-actions]

GNU testsuite comparison:

Skip an intermittent issue tests/tty/tty-eof (fails in this run but passes in the 'main' branch)

[github-actions]

GNU testsuite comparison:

Skip an intermittent issue tests/shuf/shuf-reservoir (fails in this run but passes in the 'main' branch)
Skip an intermittent issue tests/sort/sort-stale-thread-mem (fails in this run but passes in the 'main' branch)

[github-actions]

GNU testsuite comparison:

Congrats! The gnu test tests/seq/seq-epipe is now passing!

[github-actions]

GNU testsuite comparison:

Congrats! The gnu test tests/seq/seq-epipe is now passing!

[oech3]

Waiting rebase until other CI finishes.

[github-actions]

GNU testsuite comparison:

Skipping an intermittent issue tests/shuf/shuf-reservoir (passes in this run but fails in the 'main' branch)
Skipping an intermittent issue tests/sort/sort-stale-thread-mem (passes in this run but fails in the 'main' branch)

[oech3]

I'm not sure should I use RAM for FBSD too

[github-actions]

GNU testsuite comparison:

GNU test failed: tests/tail/assert. tests/tail/assert is passing on 'main'. Maybe you have to rebase?

[oech3]

@ChrisDryden @lcheylus still very slow...

[lcheylus]

@ChrisDryden @lcheylus still very slow...

That's "normal" :

• BSD OS (especially OpenBSD) are not as fast as Linux
• rustc and cargo are not as optimized on BSD as on Linux (FreeBSD = "Tier 2 with Host Tools", OpenBSD = "Tier 3")
• FreeBSD and OpenBSD are launched with a QEMU/KVM Virtual Machine on GitHub Ubuntu runner => impact on CI performance.

Why do you want to optimize the BSD CIs so much?

[oech3]

Because it is slowest one. Some PRs saving time for other CI was merged, but it does not improve test cycle if slowest one is still kept.

[oech3]

OK. I just wait your PR.

[lcheylus]

Because it is slowest one. Some PRs saving time for other CI was merged, but it does not improve test cycle if slowest one is still kept.

"OpenBSD CI" is not the longest one, it's the complete "CICD" workflow, see https://github.com/uutils/coreutils/actions/workflows/CICD.yml?query=is%3Asuccess

Even with optimizations, "OpenBSD CI" will be always slow, see my explanations above. We can not improve a "slow" OS and a Rust toolchain not well supported on this OS :(

[oech3]

CICD is a collection of parallel jobs... but you are right: CICD / Build/Makefile was slowest.