X-MimeOLE: Produced By Microsoft Exchange V6.5
Received: by onstor-exch02.onstor.net 
	id <01C7F633.B618F9A7@onstor-exch02.onstor.net>; Thu, 13 Sep 2007 10:27:16 -0800
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C7F633.B618F9A7"
References: <BB375AF679D4A34E9CA8DFA650E2B04E018A69FE@onstor-exch02.onstor.net> <20070912125628.148e9be7@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 10:25:30 -0800
Message-ID: <BB375AF679D4A34E9CA8DFA650E2B04E02F3D7ED@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: Acf1dwKP/uyJd/2KTauuQyQRnBeUzQAvHSSZ
From: "Ken Renshaw" <ken.renshaw@onstor.com>
To: "Andy Sharp" <andy.sharp@onstor.com>,
	"Jeff Miller" <jeff.miller@onstor.com>
Cc: "Maxim Kozlovsky" <maxim.kozlovsky@onstor.com>

This is a multi-part message in MIME format.

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

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)
=20
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:

>=20
>=20
> -----Original Message-----
> From: Build Admin [mailto:build@localhost.localdomain]=20
> 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
>=20
> /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
>=20
> Please check compilation logs at http://liszt for today for the dev
> branch


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

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Diso-8859-1">
<META NAME=3D"Generator" CONTENT=3D"MS Exchange Server version =
6.5.7652.24">
<TITLE>RE: Compilation failure in dev branch (to dl-Software not just =
dl-Cougar)</TITLE>
</HEAD>
<BODY>
<!-- Converted from text/plain format -->

<P><FONT SIZE=3D2>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 &quot;Error &quot; 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.<BR>
<BR>
Thanks,<BR>
<BR>
-Ken<BR>
<BR>
<BR>
-----Original Message-----<BR>
From: Andy Sharp<BR>
Sent: Wed 9/12/2007 12:56 PM<BR>
To: Jeff Miller<BR>
Cc: Ken Renshaw; Maxim Kozlovsky<BR>
Subject: Re: Compilation failure in dev branch (to dl-Software not just =
dl-Cougar)<BR>
<BR>
This is the actual log, and it's obvious that Max has broken the =
build:<BR>
<BR>
<BR>
make -C linux kernel<BR>
make[1]: Entering directory `/perforce/trees/dev/linux'<BR>
make -C kernel kernel<BR>
make[2]: Entering directory `/perforce/trees/dev/linux/kernel'<BR>
Makefile:26: Using /var/nfsroot/bobcat as root directory<BR>
make -C linux-mips-2.6 -j4<BR>
make[3]: Entering directory =
`/perforce/trees/dev/linux/kernel/linux-mips-2.6'<BR>
scripts/kconfig/conf -s arch/mips/Kconfig<BR>
*<BR>
* Restart config...<BR>
*<BR>
*<BR>
* Management Bus Driver support<BR>
*<BR>
Support for SSC Management Bus (MGMT_BUS) [Y/n/?] y<BR>
Remote console for FP and TXRX (RCON) [Y/n/?] (NEW) aborted!<BR>
<BR>
Console input/output is redirected. Run 'make oldconfig' to update =
configuratio<BR>
n.<BR>
<BR>
make[5]: *** [silentoldconfig] Error 1<BR>
make[4]: *** [silentoldconfig] Error 2<BR>
make[3]: *** [include/config/auto.conf] Error 2<BR>
make[3]: Leaving directory =
`/perforce/trees/dev/linux/kernel/linux-mips-2.6'<BR>
make[2]: *** [kernel-build] Error 2<BR>
make[2]: Leaving directory `/perforce/trees/dev/linux/kernel'<BR>
make[1]: *** [kernel] Error 2<BR>
make[1]: Leaving directory `/perforce/trees/dev/linux'<BR>
make: *** [kernel] Error 2<BR>
<BR>
<BR>
<BR>
It's also obvious that we get the wrong log sent out when we get a<BR>
broken build email message.<BR>
<BR>
Max made a check in at around 11.30 today, but it contained no =
checkin<BR>
comment!&nbsp; So I don't even know if it's related to this.<BR>
<BR>
Cheers,<BR>
<BR>
a<BR>
<BR>
<BR>
On Wed, 12 Sep 2007 11:23:30 -0700 &quot;Jeff Miller&quot;<BR>
&lt;jeff.miller@onstor.com&gt; wrote:<BR>
<BR>
&gt;<BR>
&gt;<BR>
&gt; -----Original Message-----<BR>
&gt; From: Build Admin [<A =
HREF=3D"mailto:build@localhost.localdomain">mailto:build@localhost.locald=
omain</A>]<BR>
&gt; Sent: Wednesday, September 12, 2007 6:21 AM<BR>
&gt; To: Sandrine Boulanger; Paul Hammer; Ken Renshaw; Brian =
DeForest;<BR>
&gt; dl-Cougar<BR>
&gt; Subject: Compilation failure in dev branch<BR>
&gt;<BR>
&gt; =
/perforce/buildlogs/dev/Wednesday/linux-kernel-compile.log:make[5]:<BR>
&gt; *** [silentoldconfig] Error 1<BR>
&gt; =
/perforce/buildlogs/dev/Wednesday/linux-kernel-compile.log:make[4]:<BR>
&gt; *** [silentoldconfig] Error 2<BR>
&gt; =
/perforce/buildlogs/dev/Wednesday/linux-kernel-compile.log:make[3]:<BR>
&gt; *** [include/config/auto.conf] Error 2<BR>
&gt; =
/perforce/buildlogs/dev/Wednesday/linux-kernel-compile.log:make[2]:<BR>
&gt; *** [kernel-build] Error 2<BR>
&gt; =
/perforce/buildlogs/dev/Wednesday/linux-kernel-compile.log:make[1]:<BR>
&gt; *** [kernel] Error 2<BR>
&gt; /perforce/buildlogs/dev/Wednesday/linux-kernel-compile.log:make: =
***<BR>
&gt; [kernel] Error 2<BR>
&gt;<BR>
&gt; Please check compilation logs at <A =
HREF=3D"http://liszt">http://liszt</A> for today for the dev<BR>
&gt; branch<BR>
<BR>
</FONT>
</P>

</BODY>
</HTML>
------_=_NextPart_001_01C7F633.B618F9A7--
