Closed krytarowski closed 1 year ago
Most of these failures are caused by your insufficiently setup testing machine.
Why closed?
OK, if nim is that much hostile to BSD, I have no interest either to keep any interest in nim.
I would be happy to help earlier but I lost any interest due to that treatment.
Hey, @krytarowski . Nim isn't hostile to BSD and there is ongoing work to fix those test failures (we now have CI for OpenBSD and FreeBSD), tracked in https://github.com/nim-lang/Nim/issues/14035 and https://github.com/nim-lang/Nim/issues/14075 :)
I didn't know what I was smoking 3 years ago. I deleted my comment and I apologize. @krytarowski
OK. So once OpenBSD and FreeBSD will pass the test, I can have a look at NetBSD.
OK. So once OpenBSD and FreeBSD will pass the test, I can have a look at NetBSD.
@krytarowski to clarify what @Clyybber said:
there's no need to pass tests 100% in order to start adding netbsd to nim's CI; what can be fixed in short order would be nice to fix; some tests that are harder to fix in the same PR can simply be handled by disabling those tests for netbsd, eg like this:
tests/parallel/tflowvar.nim:7:3: disabled: "netbsd"
fixing these disabled tests happens over time and is a community effort, all it takes is 1 person to start it by opening a PR.
Note that sourcehut (https://sr.ht/) has supported netbsd for some time, so you can just follow those PR's if you want to get started on this, eg with some .builds/netbsd.yml
Note: sr.ht doesn't support NetBSD, yet. I believe Drew had some problems getting a VM image to boot under the sr.ht setup. A full list of supported images on builds.sr.ht is available here. Drew put out a call for help with NetBSD a little while ago and there doesn't seem to have been much movement there (the only reference I can find is here) - if you can help at all with that @krytarowski it would help a LOT of people out and we could get the ball rolling here!
I've been working on improving the BSD support, including NetBSD. I have a couple of open issues for failing NetBSD tests that I've been running locally: #14090, #14092 and #14094. I've also fixed some other NetBSD failures: #14088, #14089, #14091 and #14093.
Until we can get NetBSD CI running properly, I've been resorting to running the tests manually locally in a VM every so often and seeing what fails and reporting some of them and fixing those I can. My last run produced the following failures:
I plan to open issues and a tracking issue for these at some point, but want to re-run the tests first to make sure this list is up to date.
@euantorano
Note: sr.ht doesn't support NetBSD, yet.
you're right, there was conflicting information about that; could docker work?
eg: docker run -it madworx/netbsd:8.0-x86_64 bash
( https://github.com/madworx/docker-netbsd , possibly spawned from a CI instance to avoid server costs)
(and another option is EC2 https://wiki.netbsd.org/amazon_ec2/)
mind sharing a guide on how you setup your VM to install nim? also do you have a meta-issue covering netbsd like you did for the other BSD? if not we could re-open this issue
Docker doesn’t work in sr.ht, but I know it does work with Travis and CircleCI. Not sure about Azure or GitHub Actions. Might be worth looking into.
On Wed, 13 May 2020, at 06:15, Timothee Cour wrote:
Note: sr.ht doesn't support NetBSD, yet.
you're right, there was conflicting information about that; could docker work? eg:
docker run -it madworx/netbsd:8.0-x86_64 bash
( https://github.com/madworx/docker-netbsd , possibly spawned from a CI instance to avoid server costs)— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/nim-lang/Nim/issues/4794#issuecomment-627751002, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAFW24MCTAHEBR4GUXJN5M3RRIUIZANCNFSM4CP674AA.
we should use either azure or github actions, for reasons of higher parallelism among other things
I now have a Jenkins instance running tests on NetBSD every day at 01:00. There are a few consistent failures that need disablements for now until I work out what's going on, as documented here.
let's turn this into a meta-issue for netbsd (like https://github.com/nim-lang/Nim/issues/14075 for freebsd and https://github.com/nim-lang/Nim/issues/14035 for openbsd) then, as well as to track progress on adding CI for netbsd (whether it'll always be run on each push/PR depends on other factors)
see also: https://github.com/nim-lang/Nim/issues?q=is%3Aissue+is%3Aopen+sort%3Aupdated-desc+netbsd
PRs are accepted but we don't have access to a NetBSD machine.