You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
If so, how should we approach it? I propose that we start by simply not building the failing tests on FreeBSD. That would provide a TODO list of components to work on for FreeBSD support.
I would be happy to try an initial pass, using the proposed approach above. I suspect at least a category of the failures are due to Linux-specific unix.* var names. One example of addressing them in a single component is at #2544.
Context
From what I can tell, CI doesn't currently verify FreeBSD.
Remove cirrus ci: It was only used for verifying freebsd buildability. We are going to use github actions for that instead (#2419)
GitHub actions doesn't officially support FreeBSD as far as I know. The method I'm aware of requires you to run a FreeBSD VM inside of a MacOS instance. That's pretty janky.
Cirrus CI runs directly on FreeBSD machines, so it should probably be re-instated for FreeBSD verification. I am happy to help with configuring it.
In #2544 (review), @rminnich suggested it would be worthwhile to bring back Cirrus CI for FreeBSD verification.
As an initial investigation, I tried running the u-root test suite on FreeBSD 13.1. Here are the failures:
Open questions
termios
, because Tailscale uses it (see Add tailssh support on FreeBSD tailscale/tailscale#6155).I would be happy to try an initial pass, using the proposed approach above. I suspect at least a category of the failures are due to Linux-specific
unix.*
var names. One example of addressing them in a single component is at #2544.Context
From what I can tell, CI doesn't currently verify FreeBSD.
#2421 says:
GitHub actions doesn't officially support FreeBSD as far as I know. The method I'm aware of requires you to run a FreeBSD VM inside of a MacOS instance. That's pretty janky.
Cirrus CI runs directly on FreeBSD machines, so it should probably be re-instated for FreeBSD verification. I am happy to help with configuring it.
In #2544 (review), @rminnich suggested it would be worthwhile to bring back Cirrus CI for FreeBSD verification.
As an initial investigation, I tried running the
u-root
test suite on FreeBSD 13.1. Here are the failures:The text was updated successfully, but these errors were encountered: