-
-
Notifications
You must be signed in to change notification settings - Fork 105
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add support for OpenBSD #1176
Comments
Sure, happy to do an OpenBSD release. But it would seem like we'd need to wait for a libc release with your patch -- is that correct? |
Yes, my PR to add |
Update for this request In the future OpenBSD stable version (7.5, scheduled for April/May 2024), cargo-nextest will be available in ports and could be installed as package. As a temporary solution, I created a GitHub workflow to build cargo-nextest binary for OpenBSD-stable (current version = 7.4) and publish it as a release sync with nextest release. See me repository https://github.com/lcheylus/cargo-nextest-openbsd
"Build and publish" GH workflow :
Build and GH workflow are OK. I publish with it a release for OpenBSD of cargo-nextest version 0.9.66 (latest release) => https://github.com/lcheylus/cargo-nextest-openbsd/releases/tag/0.9.66 |
For a Rust project, I need to add a GitHub workflow for tests on OpenBSD OS (using this GH action vmactions/openbsd-vm).
In this workflow, I'm using
nextest
to run tests viacargo nextest
.Currently, nextest build fails on OpenBSD because of an error with
waitid
C function not included inlibc
crate (included inshared_child
crate) => see my PR rust-lang/libc#3490 to fix this issue.With this patch, build on OpenBSD is OK. I created an initial OpenBSD port for
nextest
v0.9.66 , see https://github.com/jasperla/openbsd-wip/tree/master/devel/cargo-nextestI would like to have a specific
nextest
release for OpenBSD official version to download directly the resulting binary => https://get.nexte.st/latest/openbsdThat would be the simplest solution to download/install
nextest
in my GH workflow for OpenBSD.The text was updated successfully, but these errors were encountered: