Conference smurf::buildhelp

2707.0. "Can you help with bsubmit trouble in India?" by AOSG::FILTER (Automatic Posting Software - mail to flume::puck) Wed Dec 04 1996 10:02

Date Of Receipt: 	 4-DEC-1996 09:43:54.89
From: 	FLUME::gillett "Christopher Gillett USG  04-Dec-1996 0940"
To: 	[email protected]
CC: 	[email protected]
Subj: 	Can you help with bsubmit trouble in India?
Howdy Folks: 	

I'll forward you another message about this (my reply to Krishna) after
this message.

Can you help out here?  It looks like they're having a major ODE
problem of some sort (they may have shot themselves in the foot...I'm
nowhere near ready to blame ODE for this yet), and looks like a bsubmit
got trashed.  I'm not sure what the best course of action is, so would
like to ask for your assistance.

Krishna's email attached below, my reply follows next.  Anything you
can do to help him out will be most appreciated.  Remember, there is
a 10.5 hour time shift between here and Bangalore, India, so as I 
type this message it 8:10 in the evening there, so they will probably
not respond quickly to any email.  Krishna does sometimes work late
though.

Thanks very much!

Chris


------- Forwarded Message

Return-Path: [email protected] 
Delivery-Date: Wed, 04 Dec 96 08:37:33 -0500
Return-Path: [email protected]
Received: from flume.zk3.dec.com by quarry.zk3.dec.com; (5.65v3.2/1.1.8.2/16Jan95-0946AM)
	id AA28722; Wed, 4 Dec 1996 08:37:28 -0500
Received: from indus.xko.dec.com by flume.zk3.dec.com; (5.65v3.2/1.1.8.2/16Jan95-0946AM)
	id AA13308; Wed, 4 Dec 1996 08:37:35 -0500
Received: from localhost by indus.xko.dec.com (5.65v3.2/1.1.10.5/20Nov96-0538PM)
	id AA28151; Wed, 4 Dec 1996 19:07:10 +0530
Message-Id: <[email protected]>
To: [email protected]
Subject: Looks like major problem with my _bsubmit_..
Date: Wed, 04 Dec 96 19:07:10 +0530
From: [email protected]
X-Mts: smtp


Hi, Chris.

Today i was doing my bsubmit for 'steelos-1231-krishna'

I have attached 'bsubmit -verbose .... ' output for your ref.
I think, it has deleted all  revisions (done by me so far) from the
ode pool. Don't worry - i have backup of all my changes so far.

Itz first time happening to me, today i spent whole day
to find out what went wrong but couldn't find the reason.

Following are the summary of things i did today:
- ------------------------------------------------

* One thing, i did in the morning was that i created and edited
  /usr/users/krishna/Sbox/steel/src/.BCSconfig file. Actually it was
  not there in the corr directory, and bsubmit was complaining that
  entries were not found in this .BCSconfig file.

* bsubmit again failed complaining something like-
	VALIDATION FAILED
	.../errors.list locked
	.../expr_sem.c  locked
	.../symtab.c    locked

  next i unlocked this file using
  'bcs -u  errors.list, expr_sem.c, symtab.c'

See below for next.... 
- ----------------------

krishna@devil:/usr/users/krishna/Sbox/steel/src/usr/ccs/bin/cfe>cat 
../../../../.BCSconfig
./usr/ccs/bin/cfe/errors.list,v	4.2.21.2
./usr/ccs/bin/cfe/expr_sem.c,v  4.3.31.6
./usr/ccs/bin/cfe/symtab.c,v	4.3.16.2


krishna@devil:/usr/users/krishna/Sbox/steel/src/usr/ccs/bin/cfe> bsubmit 
- -verbose errors.list expr_sem.c symtab.c
>  Reading rc file : /home/indus/krishna/.sandboxrc
>  build to submit to is: steelos.
>  Time is: 17:24; date is: 12/4/96.
>  cd'ing to sandbox source directory: /usr/users/krishna/Sbox/steel/src.
>  checking for lock on build: /usr/sde/osf1/build/steelos/src/.BCSlock
>  checking access control list on submit
Outdate files if successful submission? [Y]es, [N]o, [Q]uery later]: [Yes] 
>  Checking environment...

Enter the defect number this submission applies to: steelos-1231-krishna
>  Submitting the following files:
>  ./usr/ccs/bin/cfe/errors.list
>  ./usr/ccs/bin/cfe/expr_sem.c
>  ./usr/ccs/bin/cfe/symtab.c
>  have lock on hold file.
>  checking HOLD file: 17:24.Thold /usr/sde/osf1/build/steelos/logs/bsubmit.hold
>  found no holds on files being submitted.
>  added 3 files to the hold list.
>  Validating submission...
>  base revision 4.2.21.2
>  common ancestor 4.2.21.2; will just use revision 4.2.20.4
>  No merge required
>  base revision 4.3.31.6
>  common ancestor 4.3.31.6; will just use revision 4.3.30.2
>  No merge required
>  base revision 4.3.16.2
>  common ancestor 4.3.16.2; will just use revision 4.3.15.2
>  No merge required

*** No user interaction will be required during the merge step. ***

>  Performing merge(s)...
>  ./usr/ccs/bin/cfe/errors.list
>  Retrieving revision 4.2.20.4
>  Base revision 4.2.21.2
>  Common ancestor 4.2.21.2; will just use revision 4.2.20.4
>  ./usr/ccs/bin/cfe/expr_sem.c
>  Retrieving revision 4.3.30.2
>  Base revision 4.3.31.6
>  Common ancestor 4.3.31.6; will just use revision 4.3.30.2
>  ./usr/ccs/bin/cfe/symtab.c
>  Retrieving revision 4.3.15.2
>  Base revision 4.3.16.2
>  Common ancestor 4.3.16.2; will just use revision 4.3.15.2
>  Preparing for check-in(s)...
>  Checking files in; Set: 'STEELOS'
>  ./usr/ccs/bin/cfe/errors.list
>  Scanning for HISTORY and $Log...$ messages
>> WARNING in bsubmit:
>> Empty or non-existant mesgfile.
>> File: '/usr/users/krishna/Sbox/steel/tmp/_LOG_'
>> No log information was recorded!!
ci warning: missing message for -m option
./usr/ccs/bin/cfe/errors.list,v  <--  
OdeSrvrTmpKrishna_Babu_Bangera024724/errors.list
new revision: 4.2.20.5; previous revision: 4.2.20.4
done
[ ./usr/ccs/bin/cfe/errors.list checked in onto branch 4.2.20 ]
>  Updating ./.BCSlog-Krishna_Babu_Bangera_steel
>  ./usr/ccs/bin/cfe/expr_sem.c
>  Scanning for HISTORY and $Log...$ messages
>> WARNING in bsubmit:
>> Empty or non-existant mesgfile.
>> File: '/usr/users/krishna/Sbox/steel/tmp/_LOG_'
>> No log information was recorded!!
ci warning: missing message for -m option
./usr/ccs/bin/cfe/expr_sem.c,v  <--  
OdeSrvrTmpKrishna_Babu_Bangera009469/expr_sem.c
new revision: 4.3.30.3; previous revision: 4.3.30.2
done
[ ./usr/ccs/bin/cfe/expr_sem.c checked in onto branch 4.3.30 ]
>  Updating ./.BCSlog-Krishna_Babu_Bangera_steel
>  ./usr/ccs/bin/cfe/symtab.c
>  Scanning for HISTORY and $Log...$ messages
>> WARNING in bsubmit:
>> Empty or non-existant mesgfile.
>> File: '/usr/users/krishna/Sbox/steel/tmp/_LOG_'
>> No log information was recorded!!
RCS file: ./usr/ccs/bin/cfe/symtab.c,v
4.3 locked
done
./usr/ccs/bin/cfe/symtab.c,v  <--  OdeSrvrTmpKrishna_Babu_Bangera023313/symtab.c
new revision: 4.3.17.1; previous revision: 4.3
done
RCS file: ./usr/ccs/bin/cfe/symtab.c,v
4.3 unlocked
done
RCS file: ./usr/ccs/bin/cfe/symtab.c,v
4.3.17.1 locked
done
ci warning: missing message for -m option
./usr/ccs/bin/cfe/symtab.c,v  <--  OdeSrvrTmpKrishna_Babu_Bangera010968/symtab.c
new revision: 4.3.17.2; previous revision: 4.3.17.1
done
[ ./usr/ccs/bin/cfe/symtab.c checked in onto branch 4.3.17 ]
>  Updating ./.BCSlog-Krishna_Babu_Bangera_steel
>  Updating default build; Set: 'STEELOS'
>  from directory: /usr/sde/osf1/build/steelos/src.
>  ./usr/ccs/bin/cfe/errors.list
./usr/ccs/bin/cfe/errors.list,v  -->  
OdeSrvrTmpKrishna_Babu_Bangera009566/errors.list
revision 4.2.20.5
done
[ ./usr/ccs/bin/cfe/errors.list Rev 4.2.20.5 checked out ]
>  ./usr/ccs/bin/cfe/expr_sem.c
./usr/ccs/bin/cfe/expr_sem.c,v  -->  
OdeSrvrTmpKrishna_Babu_Bangera013353/expr_sem.c
revision 4.3.30.3
done
[ ./usr/ccs/bin/cfe/expr_sem.c Rev 4.3.30.3 checked out ]
>  ./usr/ccs/bin/cfe/symtab.c
./usr/ccs/bin/cfe/symtab.c,v  -->  OdeSrvrTmpKrishna_Babu_Bangera014079/symtab.c
revision 4.3.17.2
done
[ ./usr/ccs/bin/cfe/symtab.c Rev 4.3.17.2 checked out ]
>  Updating log files...
>  Creating list of files and revisions submitted...
>  
Full name for the log: Krishna_Babu_Bangera
>  have lock on log files.
>  updating SNAPSHOT, DEFUNCT, and submit logs.
>  Finished updating log files.
>  cleaning up hold file; removing entries.
>  Outdating the submitted files from the set: Krishna_Babu_Bangera_steel
RCS file: ./usr/ccs/bin/cfe/errors.list,v
deleting revision 4.2.21.1
deleting revision 4.2.21.2
done
[ ./usr/ccs/bin/cfe/errors.list outdated revisions in set 
Krishna_Babu_Bangera_steel ]
>  Removing from ./.BCSconfig:
>  ./usr/ccs/bin/cfe/errors.list
>  ./usr/ccs/bin/cfe/errors.list,v      4.2.21.2

>  rm: removing ./usr/ccs/bin/cfe/errors.list
RCS file: ./usr/ccs/bin/cfe/expr_sem.c,v
deleting revision 4.3.31.1
deleting revision 4.3.31.2
deleting revision 4.3.31.3
deleting revision 4.3.31.4
deleting revision 4.3.31.5
deleting revision 4.3.31.6
done
[ ./usr/ccs/bin/cfe/expr_sem.c outdated revisions in set 
Krishna_Babu_Bangera_steel ]
>  Removing from ./.BCSconfig:
>  ./usr/ccs/bin/cfe/expr_sem.c
>  ./usr/ccs/bin/cfe/expr_sem.c,v       4.3.31.6

>  rm: removing ./usr/ccs/bin/cfe/expr_sem.c
RCS file: ./usr/ccs/bin/cfe/symtab.c,v
deleting revision 4.3.16.1
deleting revision 4.3.16.2
done
[ ./usr/ccs/bin/cfe/symtab.c outdated revisions in set 
Krishna_Babu_Bangera_steel ]
>  Removing from ./.BCSconfig:
>  ./usr/ccs/bin/cfe/symtab.c
>  ./usr/ccs/bin/cfe/symtab.c,v 4.3.16.2

>  rm: removing ./.BCSconfig
>  rm: removing ./.BCSset-Krishna_Babu_Bangera_steel
>  rm: removing ./.BCSlog-Krishna_Babu_Bangera_steel
>  rm: removing ./usr/ccs/bin/cfe/symtab.c

Submission completed successfully.

- -------------------------------


Chris, it didn't prompt before while removing files. And other thing
is i tried same bsubmit command with -info option. That time also it
didn't tell much  about the merge operation itz going to do.

I can extract the changes from my backup and then check-in, followed
by srequest, bsubmits.  Do you have any other alternatives for this.

I am sure i can find a better way to do this, without loosing any of
the check-in information).

Bye, and Sorry for troubling you.

Krishna.






------- End of Forwarded Message