Date: Fri, 03 Feb 2012 19:35:14 -0800 From: Doug Barton <dougb@FreeBSD.org> To: John Baldwin <jhb@freebsd.org> Cc: =?ISO-8859-1?Q?Dag-Erling_Sm=F8rgrav?= <des@des.no>, George Mitchell <george+freebsd@m5p.com>, freebsd-stable@freebsd.org, Colin Percival <cperciva@freebsd.org> Subject: Re: [releng_8_2 tinderbox] failure on powerpc/powerpc Message-ID: <4F2CA772.4060902@FreeBSD.org> In-Reply-To: <201202030834.54072.jhb@freebsd.org> References: <201202022037.q12Kb66S041860@freebsd-legacy2.sentex.ca> <4F2B278A.3080502@m5p.com> <201202030834.54072.jhb@freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On 02/03/2012 05:34, John Baldwin wrote: > On Thursday, February 02, 2012 7:17:14 pm George Mitchell wrote: >> 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 > > No, it is more that the tinderbox for 8 wasn't actually checking these > kernels before (they have been broken since 8.1 and 8.2 were released) and > they are on less-used platforms. Shouldn't whoever asked for that to be enabled take responsibility for cleaning them up then? > I do agree it needs to be cleaned up one way > or another. Given the reticence to commit changes to release branches, They're already broken. It's hard to see how fixing the problems could make things worse. :) Doug -- It's always a long day; 86400 doesn't fit into a short. Breadth of IT experience, and depth of knowledge in the DNS. Yours for the right price. :) http://SupersetSolutions.com/
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4F2CA772.4060902>