AF:
NF:0
PS:10
SRH:1
SFN:
DSR:
MID:<20071210114311.7d8df64a@ripper.onstor.net>
CFG:
PT:0
S:andy.sharp@onstor.com
RQ:
SSV:onstor-exch02.onstor.net
NSV:
SSH:
R:<brian.stark@onstor.com>
MAID:1
X-Sylpheed-Privacy-System:
X-Sylpheed-Sign:0
SCF:#mh/Mailbox/sent
RMID:#imap/andys@onstor.net@onstor-exch02.onstor.net/INBOX	0	BB375AF679D4A34E9CA8DFA650E2B04E06FCE6B7@onstor-exch02.onstor.net
X-Sylpheed-End-Special-Headers: 1
Date: Mon, 10 Dec 2007 11:44:19 -0800
From: Andrew Sharp <andy.sharp@onstor.com>
To: "Brian Stark" <brian.stark@onstor.com>
Subject: Re: This change broke cg and bl builds
Message-ID: <20071210114419.4af858ff@ripper.onstor.net>
In-Reply-To: <BB375AF679D4A34E9CA8DFA650E2B04E06FCE6B7@onstor-exch02.onstor.net>
References: <BB375AF679D4A34E9CA8DFA650E2B04E06FCE6B7@onstor-exch02.onstor.net>
Organization: Onstor
X-Mailer: Sylpheed-Claws 2.6.0 (GTK+ 2.8.20; x86_64-pc-linux-gnu)
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit

On Mon, 10 Dec 2007 11:19:00 -0800 "Brian Stark"
<brian.stark@onstor.com> wrote:

> Andy,
> 
> Before I talk with Hammer about this again, I'd like to be clear on
> one thing.  I have not received any build notifications at all since
> Thursday 12/6.  Have you been getting these?  Maybe the alias changed
> to dl-software, which I'm not part of.  Or, maybe the notifications
> just haven't been sent for some reason -- maybe these are the 3
> nights listed below, and if so, I'm not clear why I didn't get them.

AFAICT, no one has gotten any emails since Thursday.  I sure haven't,
Brian D. hasn't, Jeff hasn't....

I'm thinking this has been brought up with Hammer a few times, it's
time to bring it up with Bob.  Because if I spend time doing my own
nightly build, it might impact cougar.  Not saying it will, but not
saying it won't.  We have someone who's job it is to do this, so if I'm
spending my time on it, well, you get the idea.

> I would also say we should take the approach that we always get the
> emails, or as Ken refers to, the 'extra spam'. 

We should have an nightly build email list that people can opt inta or
outa.  The way we used to do it at 2wire was that in addition to such a
list, which most managers and senior people were on, that there was
some logic which determined who made checkins since the last successful
build (called the blame list), and emailed them as well.   Right now I'd
settle for just the list.  Or dl-software.  Or anything at all that
vaguely resembles 'working.'  Maybe I'll get in touch with my inner
feminine and burst out crying right now. That's the frustration level.

I haven't read Ken's replies, I don't have the stomach for it today.
But I can tell you that any mention of extra-spam as an excuse is pure
red herring.  Basically put, either Ken's sh!t doesn't work, or the
hardware doesn't work.  One guess where I'm putting my money.

> 
> Brian
> 
> 
> -----Original Message-----
> From: Ken Renshaw 
> Sent: Monday, December 10, 2007 11:09 AM
> To: Andy Sharp; Ron Bhanukitsiri
> Cc: Yuvarani Cothandaraman; dl-software; Paul Hammer; Brian Stark; Ken
> Renshaw
> Subject: RE: This change broke cg and bl builds
> 
> Wrong assumption Andy.
> 
> Once again I wish people would *ask* instead of *assume*, that's
> where a lot of perception comes from, and where a lot of
> communication could be fixed.
> 
> When I do work on the pass/fail logic for the nightly builds I turn
> off global notification to keep from spamming you, but always always
> send emails to myself from buildadm irregardless. Once I've tested the
> pass/fail logic by running it a day or so I reenable global
> notifications. I have dryrun flags in place but the entire process can
> only be tested live nightly, so once in a while I take this route
> ( last time was when a bsd problem was missed, can't remember the
> time before that... ).
> 
> The last email from the build failure is included below ( rest assured
> there were 3 for 3 night's worth ), and it's what I used to trigger
> Ron into fixing the problem.
> 
> My problem is that I'm going to get complaints either from the extra
> spam or from a missed email, so I choose the one that attracts the
> least attention. If you wish I can take the other route, that of
> always sending the global notifications, and then send out a 'false
> alarm' email once it has been triaged.
> 
> But as I said, builds were running, build caught the failure, and
> build worked with the ensuring developer to correct the action. Sorry
> it didn't happen before y'all showed back up from the weekend.
> 
> ------Included message-----------
> 
> -----Original Message-----
> From: Build Admin [mailto:build@localhost.localdomain]
> Sent: Mon 12/10/2007 6:25 AM
> To: Ken Renshaw
> Subject: Compilation failure in dev branch
>  
> /perforce/buildlogs/dev/Monday/bl-dbg-compile.log:make[2]: ***
> [../../Build/bl/dbg/Objects/SSC/sm-utils/cmd-utils.o] Error 1
> /perforce/buildlogs/dev/Monday/bl-dbg-compile.log:make[1]: ***
> [default] Error 1
> /perforce/buildlogs/dev/Monday/bl-dbg-compile.log:make: *** [ssc]
> Error 2
> /perforce/buildlogs/dev/Monday/bl-opt-compile.log:make[2]: ***
> [../../Build/bl/opt/Objects/SSC/sm-utils/cmd-utils.o] Error 1
> /perforce/buildlogs/dev/Monday/bl-opt-compile.log:make[1]: ***
> [default] Error 1
> /perforce/buildlogs/dev/Monday/bl-opt-compile.log:make: *** [ssc]
> Error 2
> /perforce/buildlogs/dev/Monday/cg-dbg-compile.log:make[2]: ***
> [../../Build/cg/dbg/Objects/SSC/sm-utils/cmd-utils.o] Error 1
> /perforce/buildlogs/dev/Monday/cg-dbg-compile.log:make[1]: ***
> [default] Error 1
> /perforce/buildlogs/dev/Monday/cg-dbg-compile.log:make: *** [ssc]
> Error 2
> /perforce/buildlogs/dev/Monday/cg-opt-compile.log:make[2]: ***
> [../../Build/cg/opt/Objects/SSC/sm-utils/cmd-utils.o] Error 1
> /perforce/buildlogs/dev/Monday/cg-opt-compile.log:make[1]: ***
> [default] Error 1
> /perforce/buildlogs/dev/Monday/cg-opt-compile.log:make: *** [ssc]
> Error 2
> 
> -----End included message----
> 
> Thanks,
> 
> -Ken
> 
> -----Original Message-----
> From: Andy Sharp
> Sent: Mon 12/10/2007 10:56 AM
> To: Ron Bhanukitsiri
> Cc: Ken Renshaw; Yuvarani Cothandaraman; dl-software; Paul Hammer;
> Brian Stark
> Subject: Re: This change broke cg and bl builds
>  
> No worries, Ron.
> 
> Well, almost no worries.
> 
> The breakage was checked in on Friday, but apparently no notice from
> our nightly build whatsoever.
> 
> I believe I'm correct in saying we should have been getting messages
> since Saturday informing us of the breakage?
> 
> Our engineering processes, including QA and software development, rely
> heavily on the sanctity and trustworthiness of the nightly build, but
> right now the perception is that it can't be trusted.  Can we put a
> priority on doing whatever it is that needs to be done to fix it?
> 
> Please?
> 
> Thanks,
> 
> a
> 
> 
> On Mon, 10 Dec 2007 10:36:04 -0800 "Ron Bhanukitsiri"
> <ronb@onstor.com> wrote:
> 
> > Sorry about that.  The fix has been checked in.
> > CL #26840.
> > 
> > Ron B[ee]
> > 
> > -----Original Message-----
> > From: Ken Renshaw
> > Sent: Sunday, December 09, 2007 2:05 PM
> > To: Ron Bhanukitsiri
> > Cc: Brian DeForest
> > Subject: FW: This change broke cg and bl builds
> > Importance: High
> > 
> > Hi Ron, this checkin breaks the cougar and bobcat-linux cg and bl 
> > targets, here's the error:
> > 
> > make[2]: Entering directory
> > `/perforce/trees/dev/nfx-tree/code/sm-utils' 
> > /usr/bin/mipsel-linux-gnu-gcc-4.1 -fPIC -fms-extensions 
> > -Wno-pointer-sign  -DBOBCAT -Wall -Wmissing-prototypes -g -Wall 
> > -Wmissing-prototypes -Werror -DEXTENDED_SECURITY -DNFX_KERBEROS 
> > -DNETEEE_FRAGMENT  -G 0 -DONSTOR_CHANGE -DLDAP_DEPRECATED 
> > -DOS_INCL=\"linux.h\"  -I./linux -I../../Includes/bl/SSC 
> > -I../../Includes/bl -I../../Includes/linux -I../../Includes -I. 
> > -I../../Build/bl/opt -DLANGUAGE_C -DLINUX_TEST -g -DSSC -DSSC_mips 
> > -DNFX_MOD_SSC -c cmd-utils.c -o 
> > ../../Build/bl/opt/Objects/SSC/sm-utils/cmd-utils.o
> > cmd-utils.c: In function 'utils_displayShareACL':
> > cmd-utils.c:2513: error: duplicate case value
> > cmd-utils.c:2511: error: previously used here
> > cmd-utils.c:2520: error: duplicate case value
> > cmd-utils.c:2519: error: previously used here
> > cmd-utils.c:2522: error: duplicate case value
> > cmd-utils.c:2521: error: previously used here
> > make[2]: *** [../../Build/bl/opt/Objects/SSC/sm-utils/cmd-utils.o]
> > Error 1
> > make[2]: Leaving directory
> > `/perforce/trees/dev/nfx-tree/code/sm-utils'
> > 
> > I thought I'd give you a chance to fix it before teh cougar team 
> > notices in the morning ;)
> > 
> > Thanks,
> > 
> > -Ken
> > 
> > 
> > -----Original Message-----
> > From: Build Admin [mailto:build@localhost.localdomain]
> > Sent: Sun 12/9/2007 2:02 PM
> > To: Ken Renshaw
> > Subject: 
> >  
> > Change 26825 by ronb@ronb-dev-local on 2007/12/07 19:41:10
> > 
> > 	Reviewed by: briand
> > 	
> > 	Add AT&T mkdir filesystem CLI feature.
> > 
> > Affected files ...
> > 
> > ... //depot/dev/nfx-tree/code/sm-gns/gns-api.c#4 edit ... 
> > //depot/dev/nfx-tree/code/sm-utils/cmd-utils.c#14 edit ... 
> > //depot/dev/nfx-tree/code/sm-utils/cmd-utils.h#5 edit ... 
> > //depot/dev/nfx-tree/code/ssc-cluster/cluster-gns-api.c#6 edit ...
> > //depot/dev/nfx-tree/code/ssc-nfxsh/agile-man/help_filesystem_quota_gr
> > ou
> > p_set.txt#2 edit
> > ...
> > //depot/dev/nfx-tree/code/ssc-nfxsh/agile-man/help_filesystem_quota_tr
> > ee
> > _set.txt#2 edit
> > ...
> > //depot/dev/nfx-tree/code/ssc-nfxsh/agile-man/help_filesystem_quota_us
> > er
> > _set.txt#2 edit
> > ... //depot/dev/nfx-tree/code/ssc-nfxsh/cmd_cshare.c#6 edit ... 
> > //depot/dev/nfx-tree/code/ssc-nfxsh/cmd_fsutil.c#3 edit ... 
> > //depot/dev/nfx-tree/code/ssc-nfxsh/cmd_fsutil.h#2 edit ... 
> > //depot/dev/nfx-tree/code/ssc-nfxsh/cmd_gns.c#3 edit ... 
> > //depot/dev/nfx-tree/code/ssc-nfxsh/cmd_quota.c#8 edit ... 
> > //depot/dev/nfx-tree/code/ssc-nfxsh/cmd_vol.c#27 edit
> > 
> > 
> > 
> 
