From owner-freebsd-cluster@FreeBSD.ORG Tue Jan 3 23:43:10 2012 Return-Path: Delivered-To: cluster@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 583001065670; Tue, 3 Jan 2012 23:43:09 +0000 (UTC) (envelope-from yanegomi@gmail.com) Received: from mail-tul01m020-f182.google.com (mail-tul01m020-f182.google.com [209.85.214.182]) by mx1.freebsd.org (Postfix) with ESMTP id 018968FC08; Tue, 3 Jan 2012 23:43:08 +0000 (UTC) Received: by obbwd18 with SMTP id wd18so19484502obb.13 for ; Tue, 03 Jan 2012 15:43:08 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=NxlGsgBrxRPpNMN5+8V8vDhbIQIFjo0QOVMx0R6TI54=; b=DdiIH/GlK9l9JuoyMj3ScITaP34vSy10KH+k3rNkrUfwDG/f0KDbMTOXBr1+eEHLaR lFizlU1mGDGMQdlsr5mOG3nl9kLCGl+SnUjvUMpf/1pYlZsP9+BP8EnkYNGATjCEdVA8 RvPyZXqmRwQch1j8p7bYqHR7RHbJ3r++H96RQ= MIME-Version: 1.0 Received: by 10.182.193.99 with SMTP id hn3mr46047998obc.61.1325632721824; Tue, 03 Jan 2012 15:18:41 -0800 (PST) Received: by 10.182.152.6 with HTTP; Tue, 3 Jan 2012 15:18:41 -0800 (PST) In-Reply-To: References: <201201030015.q030FwC1070840@freebsd-stable.sentex.ca> Date: Tue, 3 Jan 2012 15:18:41 -0800 Message-ID: From: Garrett Cooper To: Super Bisquit Content-Type: text/plain; charset=ISO-8859-1 Cc: cluster@freebsd.org, FreeBSD Tinderbox , Dag-Erling Smorgrav Subject: Re: [releng_9 tinderbox] failure on powerpc/powerpc X-BeenThere: freebsd-cluster@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Clustering FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 03 Jan 2012 23:43:10 -0000 On Tue, Jan 3, 2012 at 2:31 PM, Super Bisquit wrote: > I still say that the system should be built natively on powerpc equipment. That's not relevant to these errors. For some odd reason tinderbox takes 1-2 iterations to reach equilibrium when someone makes a data structure change, even a change to a header and C file are done in the same commit. It would be really nice to figure out what the issue is because this is a regular occurrence that pops up on the current@ and architecture specific mailing lists. Thanks, -Garrett