On Fri, 26 Oct 2012 15:31:50 -0700
m...@freebsd.org wrote:
> Thanks for fixes! Is the reason the public tinderbox didn't see these
> because it has explicit lists of arch/CONF kernels to build, while
> "make tinderbox" on my machine just builds all the capitalized files
> as configuration files?
On Fri, Oct 26, 2012 at 3:24 PM, Warner Losh wrote:
>
> On Oct 26, 2012, at 1:08 PM, Garrett Cooper wrote:
>
>> On Fri, Oct 26, 2012 at 10:26 AM, wrote:
>>> Running make tinderbox locally I see failures that aren't being
>>> reported by the automated tinderbox builds. I'm curious what's
>>> dif
On Oct 26, 2012, at 1:08 PM, Garrett Cooper wrote:
> On Fri, Oct 26, 2012 at 10:26 AM, wrote:
>> Running make tinderbox locally I see failures that aren't being
>> reported by the automated tinderbox builds. I'm curious what's
>> different about the environment. Failures are in the following:
On Oct 26, 2012, at 1:08 PM, Garrett Cooper wrote:
> On Fri, Oct 26, 2012 at 10:26 AM, wrote:
>> Running make tinderbox locally I see failures that aren't being
>> reported by the automated tinderbox builds. I'm curious what's
>> different about the environment. Failures are in the following:
On Fri, Oct 26, 2012 at 10:26 AM, wrote:
> Running make tinderbox locally I see failures that aren't being
> reported by the automated tinderbox builds. I'm curious what's
> different about the environment. Failures are in the following:
>
> arm ARMADAXP kernel failed, check _.arm.ARMADAXP for
Running make tinderbox locally I see failures that aren't being
reported by the automated tinderbox builds. I'm curious what's
different about the environment. Failures are in the following:
arm ARMADAXP kernel failed, check _.arm.ARMADAXP for details
mips SENTRY5 kernel failed, check _.mips.SEN
