github action: add openbsd in the ci

[sylvestre]

No description provided.

[sylvestre]

cc @lcheylus

[codspeed-hq]

CodSpeed Performance Report

Merging #9196 will not alter performance

_{Comparing sylvestre:ci-openbsd (f7ea9ac) with main (b78e067)}

Summary

✅ 123 untouched
⏩ 5 skipped¹

Footnotes

1. 5 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. ↩

[github-actions]

GNU testsuite comparison:

Skip an intermittent issue tests/misc/tee (fails in this run but passes in the 'main' branch)

[github-actions]

GNU testsuite comparison:

Skipping an intermittent issue tests/misc/tee (passes in this run but fails in the 'main' branch)

[github-actions]

GNU testsuite comparison:

Skip an intermittent issue tests/misc/tee (fails in this run but passes in the 'main' branch)

[github-actions]

GNU testsuite comparison:

Congrats! The gnu test tests/basenc/base64 is no longer failing!

[github-actions]

GNU testsuite comparison:

Skip an intermittent issue tests/tail/overlay-headers (fails in this run but passes in the 'main' branch)

[lcheylus]

@sylvestre

• I have a branch with all fixes for tests on OpenBSD. I will push a PR ASAP

• I don't really like your solution for OpenBSD CI. I prefer to create a specific shell script to run tests on OpenBSD and call it from tests workflow => no shell script (with escaping) in YAML file. See my personal fork with my OpenBSD CI => https://github.com/lcheylus/rust-coreutils/actions/runs/19196769338

• I have the same workflow for FreeBSD (specific shell script called from YAML) => need to create a PR to fix Useless GH actions for cache in FreeBSD workflow #5797

I propose to follow this plan :

• I will create a PR with all my fixes for OpenBSD tests
• after merge, you can rebase and merge this PR to add CI for OpenBSD.

In your PR, instead of disabling test for test_hostname_ip in tests/by-util/test_hostname.rs, you need to add an entry in /etc/hosts file on OpenBSD VM for reverse DNS lookup. For example, with command printf "10.0.2.15\topenbsd.my.domain openbsd\n" >> /etc/hosts

• after that, I will create 2 PR to improve CI on FreeBSD and OpenBSD.

Do you agree?

[sylvestre]

Parfait, merci !

[lcheylus]

FYI, cargo-nextest is not available in ports on OpenBSD current/amd64 (work in progress to add it in official ports tree for future release 7.9 ~May 2026).

But I have a personal repository to build cargo-nextest on OpenBSD stable/amd64 (current version 7.8) and publish release => https://github.com/lcheylus/cargo-nextest-openbsd. I use it in my personal CI for OpenBSD, see https://github.com/lcheylus/rust-coreutils/actions/runs/19196769338/job/54878888735

LATEST_NEXTEST_URL=$(curl -sLf https://api.github.com/repos/lcheylus/cargo-nextest-openbsd/releases/latest | grep 'download_url' | cut -d\" -f4)
curl -LsSf "${LATEST_NEXTEST_URL}" | tar zxf - -C "${HOME}"/.cargo/bin

[lcheylus]

PR #9200 created to fix tests on OpenBSD current/amd64 with Rust 1.90.0.

[sylvestre]

@lcheylus

any idea how to fix this ?

     Compiling selinux-sys v0.6.15
     Compiling fts-sys v0.2.17
  error: failed to run custom build command for `fts-sys v0.2.17`
  note: To improve backtraces for build dependencies, set the CARGO_PROFILE_DEV_BUILD_OVERRIDE_DEBUG=true environment variable to enable debug information generation.
  Caused by:
    process didn't exit successfully: `/home/runner/work/coreutils/coreutils/target/debug/build/fts-sys-28360bbb4db8ec3c/build-script-build` (exit status: 101)
    --- stdout
    cargo:root=/home/runner/work/coreutils/coreutils/target/debug/build/fts-sys-089f4b3d630caabd/out
    cargo:rerun-if-env-changed=SYSROOT_x86_64-unknown-openbsd
    cargo:rerun-if-env-changed=SYSROOT_x86_64_unknown_openbsd
    cargo:rerun-if-env-changed=TARGET_SYSROOT
    cargo:rerun-if-env-changed=SYSROOT
    cargo:rerun-if-env-changed=TARGET
    cargo:rerun-if-env-changed=BINDGEN_EXTRA_CLANG_ARGS_x86_64-unknown-openbsd
    cargo:rerun-if-env-changed=BINDGEN_EXTRA_CLANG_ARGS_x86_64_unknown_openbsd
    cargo:rerun-if-env-changed=BINDGEN_EXTRA_CLANG_ARGS
    cargo:rerun-if-changed=src/fts-sys.h
    --- stderr
    thread 'main' panicked at /home/tester/.cargo/registry/src/index.crates.io-1949cf8c6b5b557f/bindgen-0.72.1/lib.rs:616:27:
    Unable to find libclang: "couldn't find any valid shared libraries matching: ['libclang.so', 'libclang.so.*'], set the `LIBCLANG_PATH` environment variable to a path where one of these files can be found (invalid: [])"
    stack backtrace:
       0: __rustc::rust_begin_unwind
       1: core::panicking::panic_fmt
       2: core::result::unwrap_failed
       3: core::result::Result<T,E>::expect
       4: bindgen::ensure_libclang_is_loaded::{{closure}}
       5: std::sync::once_lock::OnceLock<T>::get_or_init::{{closure}}
       6: std::sync::once_lock::OnceLock<T>::initialize::{{closure}}
       7: std::sync::poison::once::Once::call_once_force::{{closure}}
       8: std::sys::sync::once::futex::Once::call
       9: std::sync::poison::once::Once::call_once_force
      10: std::sync::once_lock::OnceLock<T>::initialize
      11: std::sync::once_lock::OnceLock<T>::get_or_try_init
      12: std::sync::once_lock::OnceLock<T>::get_or_init
      13: bindgen::ensure_libclang_is_loaded
      14: bindgen::Bindings::generate
      15: bindgen::Builder::generate
      16: build_script_build::generate_bindings
      17: build_script_build::main
      18: core::ops::function::FnOnce::call_once
    note: Some details are omitted, run with `RUST_BACKTRACE=full` for a verbose backtrace.
  warning: build failed, waiting for other jobs to finish...
  gmake: *** [GNUmakefile:345: build-coreutils] Error 101

[sylvestre]

@oech3 thanks!

[oech3]

Please edit 1st comment to "Fixes #5597" before merging.

[cakebaker]

@oech3 thanks for the hint, I linked the issue.

[cakebaker]

I guess the big difference in the duration of the "tests" job (~31 minutes vs ~9 minutes with FreeBSD) is because of cargo test?

[oech3]

maybe. nextest has some tests not in make test (e.g. LD_PRELOAD libstdbuf).

[lcheylus]

I guess the big difference in the duration of the "tests" job (~31 minutes vs ~9 minutes with FreeBSD) is because of cargo test?

Mainly because OpenBSD OS is slower than FreeBSD (or Linux) :(

With my personal OpenBSD CI with cargo-nextest, last run for tests job ends in ~23 minutes (see https://github.com/lcheylus/rust-coreutils/actions/runs/19263899980).

After merge of this PR by @sylvestre, I will improve the "OpenBSD CI" and propose to replace GH action vmactions/openbsd-vm by cross-platform-actions/action with OpenBSD VM (more reliable and runs faster).

[oech3]

Cannot 1 repository run 2+ openbsd runners? They are failing with no reasons.

[lcheylus]

Cannot 1 repository run 2+ openbsd runners? They are failing with no reasons.

See issue #9241