From mboxrd@z Thu Jan 1 00:00:00 1970 From: Ian Campbell Subject: Re: [osstest PATCH] target_cmd_build: honour DistccHosts host property Date: Fri, 29 Nov 2013 08:28:34 +0000 Message-ID: <1385713714.23632.22.camel@dagon.hellion.org.uk> References: <21143.35146.795471.495670@mariner.uk.xensource.com> <21143.35468.275534.482654@mariner.uk.xensource.com> <21143.36690.700012.147813@mariner.uk.xensource.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <21143.36690.700012.147813@mariner.uk.xensource.com> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xen.org Errors-To: xen-devel-bounces@lists.xen.org To: Ian Jackson Cc: xen-devel@lists.xen.org List-Id: xen-devel@lists.xenproject.org On Thu, 2013-11-28 at 18:45 +0000, Ian Jackson wrote: > Ian Jackson writes ("Re: [osstest PATCH] target_cmd_build: honour DistccHosts host property"): > > Here's a fix to this. > > > > I have not pushed this to pretest yet because I want to be sure we get > > a pass to fix the freebsd hostflags problem and I'm not 100.000% sure > > that this change will pass. > > > > For now it's in xenbits.xen.org:/home/iwj/ext/osstest.git#wip.distcc > > It passed my ad-hoc smoke test; ts-xen-build on army now passes for me > with these two patches. ts-kernel-build was the problematic one WRT timing out. I think, entirely anecdotally, it was worse overnight if it hit my nightly Xen build cronjob (at 0028). Now that we have the osstest stuff running that is a bit obsolete, I could kill it I suppose. Also, won't you need to increase the -j flag setting 'shared max tasks' for army for this stuff to make any difference? Ian.