X-MimeOLE: Produced By Microsoft Exchange V6.5
Received: by onstor-exch02.onstor.net 
	id <01C7F64C.7FC6D2E4@onstor-exch02.onstor.net>; Thu, 13 Sep 2007 13:24:42 -0800
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C7F64C.7FC6D2E4"
References: <BB375AF679D4A34E9CA8DFA650E2B04E018A69FE@onstor-exch02.onstor.net><20070912125628.148e9be7@ripper.onstor.net><BB375AF679D4A34E9CA8DFA650E2B04E02F3D7ED@onstor-exch02.onstor.net> <20070913141858.34f394d8@ripper.onstor.net>
Content-class: urn:content-classes:message
Subject: RE: Compilation failure in dev branch (to dl-Software not just dl-Cougar)
Date: Thu, 13 Sep 2007 13:20:54 -0800
Message-ID: <BB375AF679D4A34E9CA8DFA650E2B04E02F3D7F0@onstor-exch02.onstor.net>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: Compilation failure in dev branch (to dl-Software not just dl-Cougar)
Thread-Index: Acf2S7UwiRs0qSY2RlOsRsEk+b2u2gAAEKcJ
From: "Ken Renshaw" <ken.renshaw@onstor.com>
To: "Andy Sharp" <andy.sharp@onstor.com>
Cc: "Jeff Miller" <jeff.miller@onstor.com>,
	"Maxim Kozlovsky" <maxim.kozlovsky@onstor.com>

This is a multi-part message in MIME format.

------_=_NextPart_001_01C7F64C.7FC6D2E4
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

No worries Andy, the error output is admittedly ambiguous at best, I =
just use the lines from grep to count the errors and flag a bad build so =
they were handy. I think it would be much better to include say 40 lines =
of context before each error from each logfile and prefix the snippet =
with a title giving the link to the full log. Point and click, right? ;)
=20
Thanks,
=20
-Ken

________________________________

From: Andy Sharp
Sent: Thu 9/13/2007 2:18 PM
To: Ken Renshaw
Cc: Jeff Miller; Maxim Kozlovsky
Subject: Re: Compilation failure in dev branch (to dl-Software not just =
dl-Cougar)



What I meant about Max was that it was his checkin that broke the
build, at least that's the way it looked to me.

By the wrong log, it looks to me that there are multiple logs
generated, one for each of several "sub-sections" of the build.
Instead of sending the output of the log, instead it seems to send the
name of the log where the error is or something.  Or maybe it's just the
wrong part of the log or something.  Now I'm not so sure.

OK, maybe what is wrong is that instead of a grep, it just send the
last 40 lines of the log with the breakage.  I think it's the grep that
got me confused.

OK, that's exactly what you just said, nm.

On Thu, 13 Sep 2007 11:25:30 -0700 "Ken Renshaw"
<ken.renshaw@onstor.com> wrote:

> I don't know about your statements regarding Max, but the body of the
> email sent out for the failure was from the correct log. It's simply
> the grep of "Error " from the full log, it's obviously the same error
> messages. What I think I'll do is send the last 100 lines of the log
> leading up to the error so there's some context for you guys.
>
> Thanks,
>
> -Ken
>
>
> -----Original Message-----
> From: Andy Sharp
> Sent: Wed 9/12/2007 12:56 PM
> To: Jeff Miller
> Cc: Ken Renshaw; Maxim Kozlovsky
> Subject: Re: Compilation failure in dev branch (to dl-Software not
> just dl-Cougar)
> This is the actual log, and it's obvious that Max has broken the
> build:
>
>
> make -C linux kernel
> make[1]: Entering directory `/perforce/trees/dev/linux'
> make -C kernel kernel
> make[2]: Entering directory `/perforce/trees/dev/linux/kernel'
> Makefile:26: Using /var/nfsroot/bobcat as root directory
> make -C linux-mips-2.6 -j4
> make[3]: Entering directory
> `/perforce/trees/dev/linux/kernel/linux-mips-2.6'
> scripts/kconfig/conf -s arch/mips/Kconfig *
> * Restart config...
> *
> *
> * Management Bus Driver support
> *
> Support for SSC Management Bus (MGMT_BUS) [Y/n/?] y
> Remote console for FP and TXRX (RCON) [Y/n/?] (NEW) aborted!
>
> Console input/output is redirected. Run 'make oldconfig' to update
> configuratio n.
>
> make[5]: *** [silentoldconfig] Error 1
> make[4]: *** [silentoldconfig] Error 2
> make[3]: *** [include/config/auto.conf] Error 2
> make[3]: Leaving directory
> `/perforce/trees/dev/linux/kernel/linux-mips-2.6' make[2]: ***
> [kernel-build] Error 2 make[2]: Leaving directory
> `/perforce/trees/dev/linux/kernel' make[1]: *** [kernel] Error 2
> make[1]: Leaving directory `/perforce/trees/dev/linux'
> make: *** [kernel] Error 2
>
>
>
> It's also obvious that we get the wrong log sent out when we get a
> broken build email message.
>
> Max made a check in at around 11.30 today, but it contained no checkin
> comment!  So I don't even know if it's related to this.
>
> Cheers,
>
> a
>
>
> On Wed, 12 Sep 2007 11:23:30 -0700 "Jeff Miller"
> <jeff.miller@onstor.com> wrote:
>
> >
> >
> > -----Original Message-----
> > From: Build Admin [mailto:build@localhost.localdomain]
> > Sent: Wednesday, September 12, 2007 6:21 AM
> > To: Sandrine Boulanger; Paul Hammer; Ken Renshaw; Brian DeForest;
> > dl-Cougar
> > Subject: Compilation failure in dev branch
> >
> > /perforce/buildlogs/dev/Wednesday/linux-kernel-compile.log:make[5]:
> > *** [silentoldconfig] Error 1
> > /perforce/buildlogs/dev/Wednesday/linux-kernel-compile.log:make[4]:
> > *** [silentoldconfig] Error 2
> > /perforce/buildlogs/dev/Wednesday/linux-kernel-compile.log:make[3]:
> > *** [include/config/auto.conf] Error 2
> > /perforce/buildlogs/dev/Wednesday/linux-kernel-compile.log:make[2]:
> > *** [kernel-build] Error 2
> > /perforce/buildlogs/dev/Wednesday/linux-kernel-compile.log:make[1]:
> > *** [kernel] Error 2
> > /perforce/buildlogs/dev/Wednesday/linux-kernel-compile.log:make: ***
> > [kernel] Error 2
> >
> > Please check compilation logs at http://liszt <http://liszt/>  for =
today for the dev
> > branch
>



------_=_NextPart_001_01C7F64C.7FC6D2E4
Content-Type: text/html;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<HTML dir=3Dltr><HEAD><TITLE>Re: Compilation failure in dev branch (to =
dl-Software not just dl-Cougar)</TITLE>=0A=
<META http-equiv=3DContent-Type content=3D"text/html; charset=3Dunicode">=0A=
<META content=3D"MSHTML 6.00.2800.1106" name=3DGENERATOR></HEAD>=0A=
<BODY>=0A=
<DIV id=3DidOWAReplyText74193 dir=3Dltr>=0A=
<DIV dir=3Dltr><FONT face=3DArial color=3D#000000 size=3D2>No worries =
Andy,&nbsp;the error output is&nbsp;admittedly ambiguous at best,&nbsp;I =
just use the lines from grep to count the&nbsp;errors and flag a bad =
build so they were handy. I&nbsp;think it would be&nbsp;much better =
to&nbsp;include say 40 lines of context before each error from each =
logfile and prefix the snippet with a title giving the link to the full =
log. Point and click, right? ;)</FONT></DIV>=0A=
<DIV dir=3Dltr><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>=0A=
<DIV dir=3Dltr><FONT face=3DArial size=3D2>Thanks,</FONT></DIV>=0A=
<DIV dir=3Dltr><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>=0A=
<DIV dir=3Dltr><FONT face=3DArial size=3D2>-Ken</FONT></DIV></DIV>=0A=
<DIV dir=3Dltr><BR>=0A=
<HR tabIndex=3D-1>=0A=
<FONT face=3DTahoma size=3D2><B>From:</B> Andy Sharp<BR><B>Sent:</B> Thu =
9/13/2007 2:18 PM<BR><B>To:</B> Ken Renshaw<BR><B>Cc:</B> Jeff Miller; =
Maxim Kozlovsky<BR><B>Subject:</B> Re: Compilation failure in dev branch =
(to dl-Software not just dl-Cougar)<BR></FONT><BR></DIV>=0A=
<DIV>=0A=
<P><FONT size=3D2>What I meant about Max was that it was his checkin =
that broke the<BR>build, at least that's the way it looked to =
me.<BR><BR>By the wrong log, it looks to me that there are multiple =
logs<BR>generated, one for each of several "sub-sections" of the =
build.<BR>Instead of sending the output of the log, instead it seems to =
send the<BR>name of the log where the error is or something.&nbsp; Or =
maybe it's just the<BR>wrong part of the log or something.&nbsp; Now I'm =
not so sure.<BR><BR>OK, maybe what is wrong is that instead of a grep, =
it just send the<BR>last 40 lines of the log with the breakage.&nbsp; I =
think it's the grep that<BR>got me confused.<BR><BR>OK, that's exactly =
what you just said, nm.<BR><BR>On Thu, 13 Sep 2007 11:25:30 -0700 "Ken =
Renshaw"<BR>&lt;ken.renshaw@onstor.com&gt; wrote:<BR><BR>&gt; I don't =
know about your statements regarding Max, but the body of the<BR>&gt; =
email sent out for the failure was from the correct log. It's =
simply<BR>&gt; the grep of "Error " from the full log, it's obviously =
the same error<BR>&gt; messages. What I think I'll do is send the last =
100 lines of the log<BR>&gt; leading up to the error so there's some =
context for you guys.<BR>&gt;<BR>&gt; Thanks,<BR>&gt;<BR>&gt; =
-Ken<BR>&gt;<BR>&gt;<BR>&gt; -----Original Message-----<BR>&gt; From: =
Andy Sharp<BR>&gt; Sent: Wed 9/12/2007 12:56 PM<BR>&gt; To: Jeff =
Miller<BR>&gt; Cc: Ken Renshaw; Maxim Kozlovsky<BR>&gt; Subject: Re: =
Compilation failure in dev branch (to dl-Software not<BR>&gt; just =
dl-Cougar)<BR>&gt; This is the actual log, and it's obvious that Max has =
broken the<BR>&gt; build:<BR>&gt;<BR>&gt;<BR>&gt; make -C linux =
kernel<BR>&gt; make[1]: Entering directory =
`/perforce/trees/dev/linux'<BR>&gt; make -C kernel kernel<BR>&gt; =
make[2]: Entering directory `/perforce/trees/dev/linux/kernel'<BR>&gt; =
Makefile:26: Using /var/nfsroot/bobcat as root directory<BR>&gt; make -C =
linux-mips-2.6 -j4<BR>&gt; make[3]: Entering directory<BR>&gt; =
`/perforce/trees/dev/linux/kernel/linux-mips-2.6'<BR>&gt; =
scripts/kconfig/conf -s arch/mips/Kconfig *<BR>&gt; * Restart =
config...<BR>&gt; *<BR>&gt; *<BR>&gt; * Management Bus Driver =
support<BR>&gt; *<BR>&gt; Support for SSC Management Bus (MGMT_BUS) =
[Y/n/?] y<BR>&gt; Remote console for FP and TXRX (RCON) [Y/n/?] (NEW) =
aborted!<BR>&gt;<BR>&gt; Console input/output is redirected. Run 'make =
oldconfig' to update<BR>&gt; configuratio n.<BR>&gt;<BR>&gt; make[5]: =
*** [silentoldconfig] Error 1<BR>&gt; make[4]: *** [silentoldconfig] =
Error 2<BR>&gt; make[3]: *** [include/config/auto.conf] Error 2<BR>&gt; =
make[3]: Leaving directory<BR>&gt; =
`/perforce/trees/dev/linux/kernel/linux-mips-2.6' make[2]: ***<BR>&gt; =
[kernel-build] Error 2 make[2]: Leaving directory<BR>&gt; =
`/perforce/trees/dev/linux/kernel' make[1]: *** [kernel] Error 2<BR>&gt; =
make[1]: Leaving directory `/perforce/trees/dev/linux'<BR>&gt; make: *** =
[kernel] Error 2<BR>&gt;<BR>&gt;<BR>&gt;<BR>&gt; It's also obvious that =
we get the wrong log sent out when we get a<BR>&gt; broken build email =
message.<BR>&gt;<BR>&gt; Max made a check in at around 11.30 today, but =
it contained no checkin<BR>&gt; comment!&nbsp; So I don't even know if =
it's related to this.<BR>&gt;<BR>&gt; Cheers,<BR>&gt;<BR>&gt; =
a<BR>&gt;<BR>&gt;<BR>&gt; On Wed, 12 Sep 2007 11:23:30 -0700 "Jeff =
Miller"<BR>&gt; &lt;jeff.miller@onstor.com&gt; wrote:<BR>&gt;<BR>&gt; =
&gt;<BR>&gt; &gt;<BR>&gt; &gt; -----Original Message-----<BR>&gt; &gt; =
From: Build Admin [<A =
href=3D"mailto:build@localhost.localdomain">mailto:build@localhost.locald=
omain</A>]<BR>&gt; &gt; Sent: Wednesday, September 12, 2007 6:21 =
AM<BR>&gt; &gt; To: Sandrine Boulanger; Paul Hammer; Ken Renshaw; Brian =
DeForest;<BR>&gt; &gt; dl-Cougar<BR>&gt; &gt; Subject: Compilation =
failure in dev branch<BR>&gt; &gt;<BR>&gt; &gt; =
/perforce/buildlogs/dev/Wednesday/linux-kernel-compile.log:make[5]:<BR>&g=
t; &gt; *** [silentoldconfig] Error 1<BR>&gt; &gt; =
/perforce/buildlogs/dev/Wednesday/linux-kernel-compile.log:make[4]:<BR>&g=
t; &gt; *** [silentoldconfig] Error 2<BR>&gt; &gt; =
/perforce/buildlogs/dev/Wednesday/linux-kernel-compile.log:make[3]:<BR>&g=
t; &gt; *** [include/config/auto.conf] Error 2<BR>&gt; &gt; =
/perforce/buildlogs/dev/Wednesday/linux-kernel-compile.log:make[2]:<BR>&g=
t; &gt; *** [kernel-build] Error 2<BR>&gt; &gt; =
/perforce/buildlogs/dev/Wednesday/linux-kernel-compile.log:make[1]:<BR>&g=
t; &gt; *** [kernel] Error 2<BR>&gt; &gt; =
/perforce/buildlogs/dev/Wednesday/linux-kernel-compile.log:make: =
***<BR>&gt; &gt; [kernel] Error 2<BR>&gt; &gt;<BR>&gt; &gt; Please check =
compilation logs at <A href=3D"http://liszt/">http://liszt</A> for today =
for the dev<BR>&gt; &gt; =
branch<BR>&gt;<BR></FONT></P></DIV></BODY></HTML>
------_=_NextPart_001_01C7F64C.7FC6D2E4--
