From owner-freebsd-stable@FreeBSD.ORG Fri Feb 3 00:17:21 2012 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id E1F071065670 for ; Fri, 3 Feb 2012 00:17:21 +0000 (UTC) (envelope-from george+freebsd@m5p.com) Received: from mailhost.m5p.com (ip-2-2-0-2.r20.asbnva02.us.ce.gin.ntt.net [IPv6:2001:418:0:5000::16]) by mx1.freebsd.org (Postfix) with ESMTP id 7A1838FC19 for ; Fri, 3 Feb 2012 00:17:21 +0000 (UTC) Received: from wonderland.m5p.com (wonderland.m5p.com [IPv6:2001:418:3fd::19]) by mailhost.m5p.com (8.14.4/8.14.4) with ESMTP id q130HEsM049790 for ; Thu, 2 Feb 2012 19:17:19 -0500 (EST) (envelope-from george+freebsd@m5p.com) Message-ID: <4F2B278A.3080502@m5p.com> Date: Thu, 02 Feb 2012 19:17:14 -0500 From: George Mitchell User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:9.0) Gecko/20120122 Thunderbird/9.0 MIME-Version: 1.0 To: freebsd-stable@freebsd.org References: <201202022037.q12Kb66S041860@freebsd-legacy2.sentex.ca> In-Reply-To: <201202022037.q12Kb66S041860@freebsd-legacy2.sentex.ca> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Greylist: Sender passed SPF test, not delayed by milter-greylist-4.2.7 (mailhost.m5p.com [IPv6:2001:418:3fd::f7]); Thu, 02 Feb 2012 19:17:19 -0500 (EST) X-Scanned-By: MIMEDefang 2.72 on IPv6:2001:418:3fd::f7 Subject: Re: [releng_8_2 tinderbox] failure on powerpc/powerpc X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 03 Feb 2012 00:17:22 -0000 On 02/02/12 15:37, FreeBSD Tinderbox wrote: > [... one of three errors it's been reporting repeatedly for days ...] Talk about a lack of focus! Apparently two or three people have all recently checked in code without first verifying that it compiled (let alone ran), or else possibly did not completely commit their changes, and then absconded to a place where they fail to receive these emails about the problems. Can someone please either diagnose these errors or else revert the deficient commits? -- George Mitchell