Skip site navigation (1)Skip section navigation (2)
Date:      Fri, 03 Feb 2012 15:08:19 +0100
From:      =?utf-8?Q?Dag-Erling_Sm=C3=B8rgrav?= <des@des.no>
To:        Jeremy Chadwick <freebsd@jdc.parodius.com>
Cc:        George Mitchell <george+freebsd@m5p.com>, freebsd-stable@freebsd.org
Subject:   Re: sentex tinderbox build cluster failures
Message-ID:  <861uqcko18.fsf@ds4.des.no>
In-Reply-To: <20120203084817.GA17447@icarus.home.lan> (Jeremy Chadwick's message of "Fri, 3 Feb 2012 00:48:17 -0800")
References:  <20120203084817.GA17447@icarus.home.lan>

next in thread | previous in thread | raw e-mail | index | archive | help
Jeremy Chadwick <freebsd@jdc.parodius.com> writes:
> For many days now (almost a week?) there have been tinderbox build mails
> coming from the sentex.ca build cluster, specific to powerpc, mips, and
> sparc64 platforms.
>
> The errors in question are strange and may indicate some kind of
> filesystem corruption or equivalent -- I'm really not sure.

You could have taken the time to check the code before jumping to
conclusions about "filesystem corruption or equivalent".  These are
genuine bugs.  The tinderbox didn't warn about them earlier because it
didn't build other kernels than LINT and GENERIC, and these bugs are in
machine-dependent code that isn't included in LINT and GENERIC.  I
enabled additional kernels after the arm / mips people complained that
the arm / mips build was sometimes broken for weeks without anybody
noticing.

DES
--=20
Dag-Erling Sm=C3=B8rgrav - des@des.no



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?861uqcko18.fsf>