From owner-freebsd-current@FreeBSD.ORG  Thu Apr  5 19:43:06 2012
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Delivered-To: current@freebsd.org
Received: from mx2.freebsd.org (mx2.freebsd.org [69.147.83.53])
	by hub.freebsd.org (Postfix) with ESMTP id 680EF1065675;
	Thu,  5 Apr 2012 19:43:06 +0000 (UTC)
	(envelope-from dougb@FreeBSD.org)
Received: from [127.0.0.1] (hub.freebsd.org [IPv6:2001:4f8:fff6::36])
	by mx2.freebsd.org (Postfix) with ESMTP id BD4F52014FE;
	Thu,  5 Apr 2012 19:41:49 +0000 (UTC)
Message-ID: <4F7DF57D.8010108@FreeBSD.org>
Date: Thu, 05 Apr 2012 12:41:49 -0700
From: Doug Barton <dougb@FreeBSD.org>
Organization: http://www.FreeBSD.org/
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64;
	rv:11.0) Gecko/20120327 Thunderbird/11.0.1
MIME-Version: 1.0
To: Juli Mallett <jmallett@FreeBSD.org>
References: <CACVs6=_kNJQZLouh6b+W9Ktj-CUFyeg7MVhas1qzoLGymJL7Kg@mail.gmail.com>
In-Reply-To: <CACVs6=_kNJQZLouh6b+W9Ktj-CUFyeg7MVhas1qzoLGymJL7Kg@mail.gmail.com>
X-Enigmail-Version: 1.4
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Cc: Garrett Cooper <yanegomi@gmail.com>, mips@freebsd.org,
	FreeBSD Tinderbox <tinderbox@freebsd.org>, current@freebsd.org
Subject: Re: There is a known problem with MIPS tinderbox.
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Discussions about the use of FreeBSD-current
	<freebsd-current.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>, 
	<mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
	<mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Thu, 05 Apr 2012 19:43:06 -0000

On 4/5/2012 12:39 PM, Juli Mallett wrote:
> You have not broken the MIPS tinderbox.  It has been broken for a
> couple of weeks now, and is a known problem, and hopefully will be
> fixed soon.

*phew* Thanks for letting me know. :)

Doug