Go testing for DragonFly

Brad Fitzpatrick showed up on the users@ list and mentioned that for DragonFly to be supported in Go, it needed to show up in the Go Dashboard with building reports.  I now have the Go builder running on pkgbox32/pkgbox64.dragonflybsd.org.  Check the builder page to see status.

Note: Installing the port of Go from Dports works just fine; this is the mechanism for testing Go on a per-commit basis for the people who work on Go – so a ‘fail’ notice on the builder page doesn’t necessarily mean anything, unless you are developing Go itself.  This may already be clear to you.

2 Replies to “Go testing for DragonFly”

  1. Thanks for putting this together, Justin.
    I think we should pay attention to fail messages though, especially when it alternatives between pass and fail as much as it does, it could be issues with the OS (or builder system) and not Go necessarily.

  2. It could be – though I see a lot of on-again, off-again failures with the other operating systems, so my assumption is that there’s a lot of noise. I’ve never even dabbled in Go, so the build system is still mysterious. But interesting!

Comments are closed.