Date: Sat, 10 Jul 2010 11:28:28 +0200 From: Bernhard Froehlich <decke@FreeBSD.org> To: Lars Engels <lars.engels@0x20.net> Cc: Dominic Fandrey <kamikaze@bsdforen.de>, freebsd-ports@freebsd.org, Shaun Amott <shaun@FreeBSD.org> Subject: Re: Solutions for the PR load problem Message-ID: <8de42f8685d6371428f6dc2aca7fb2f0@bluelife.at> In-Reply-To: <20100710090038.GB16045@e.0x20.net> References: <4C374B3E.90704@bsdforen.de> <20100709172503.GA22795@charon.picobyte.net> <4C375E47.9020307@bsdforen.de> <20100709200016.GA23404@charon.picobyte.net> <4C378BB5.2080206@bsdforen.de> <20100710090038.GB16045@e.0x20.net>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sat, 10 Jul 2010 11:00:38 +0200, Lars Engels <lars.engels@0x20.net> wrote: > On Fri, Jul 09, 2010 at 10:51:01PM +0200, Dominic Fandrey wrote: >> On 09/07/2010 22:00, Shaun Amott wrote: >> > >> > I'm not sure how many non-committers were aware of / given access to >> > tb3 >> > and tb4 when they were around, but if tinderbox were used as a matter >> > of >> > course, it would, I believe go some way to speeding things up. >> > >> >> So if I set up a private tinderbox and provide amd64 and i386 >> 6-/7-/8-stable logs with every PR I submit it would hasten the >> processing of my PRs? > > The more complex a port is and the more dependencies it has the more > work a committer has to check if the PR is error-free. > Having TB-Logs would prove that the port builds fine, and the PR is more > likely to be taken. Exactly for this reason beat@ has created a Tinderbox Virtual Machine for virtualbox. So port maintainers can test their updates in a tinderbox and discover problems earlier without the need of a dedicated tinderbox machine and all the setup woes. http://vboxtindi.chruetertee.ch/ -- Bernhard Froehlich http://www.bluelife.at/
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?8de42f8685d6371428f6dc2aca7fb2f0>