<div dir="ltr"><br><div class="gmail_extra"><br><br><div class="gmail_quote">On Fri, Jan 17, 2014 at 11:07 AM, John Marino <span dir="ltr"><<a href="mailto:dragonflybsd@marino.st" target="_blank">dragonflybsd@marino.st</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div class="im">On 1/17/2014 20:04, Justin Sherrill wrote:<br>
> On Fri, Jan 17, 2014 at 1:45 PM, Brad Fitzpatrick <<a href="mailto:bradfitz@golang.org">bradfitz@golang.org</a><br>
</div><div><div class="h5">> <mailto:<a href="mailto:bradfitz@golang.org">bradfitz@golang.org</a>>> wrote:<br>
><br>
><br>
> But the Go 1.2 you have already in ports might be sufficient to<br>
> build the builder worker and start the process. Even the plan9 and<br>
> solaris ports started with months of red failure on our dashboard.<br>
><br>
><br>
> The best long-term solution is to have a DragonFly system doing<br>
> bleeding-edge Go builds in a loop, correct? Even if it builds in<br>
> (d)ports, that won't catch possible problems until the port itself is<br>
> updated, and I'm assuming the purpose of this is to serve as a sort of<br>
> tinderbox/warning system.<br>
><br>
> If I can scare up a separate machine to do it, I'd be happy to build it.<br>
> I've been meaning to do something with Go, but like any project,<br>
> without a clear work target it's been hard to get started.<br>
<br>
</div></div>Justin,<br>
Rather than look for a separate machine, I suggest we add these to<br>
pkgbox64 and pkgbox32 official servers. Then you can tend them there.<br>
<br>
I doubt it's a loop though, it is probably triggered. Maybe even as<br>
often as every new commit.</blockquote><div><br></div><div>Yes, every commit.</div><div><br></div><div>The builder program monitors the build master for work. When the master sees new commits, it notifies each worker to do a new build and report the results/output.</div>
<div> </div><div>The build worker (that you will run) will just run all.bash.</div><div><br></div></div><br></div></div>