Initial add of defaria.com
[clearscm.git] / defaria.com / blogs / Status / archives / week_2004_02_08.html
1 <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"
2    "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
3 <html xmlns="http://www.w3.org/1999/xhtml" id="sixapart-standard">
4 <head>
5    <meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
6    <meta name="generator" content="Movable Type 5.2.3" />
7
8    <link rel="stylesheet" href="http://defaria.com/blogs/Status/styles-site.css" type="text/css" />
9    <link rel="alternate" type="application/atom+xml" title="Atom" href="http://defaria.com/blogs/Status/atom.xml" />
10    <link rel="alternate" type="application/rss+xml" title="RSS 2.0" href="http://defaria.com/blogs/Status/index.xml"$>" />
11
12    <title>Status for Andrew DeFaria: February  8, 2004 - February 14, 2004 Archives</title>
13
14    <link rel="start" href="http://defaria.com/blogs/Status/" title="Home" />
15    <link rel="prev" href="http://defaria.com/blogs/Status/archives/week_2004_02_01.html" title="February  1, 2004 - February  7, 2004" />
16    <link rel="next" href="http://defaria.com/blogs/Status/archives/week_2004_02_15.html" title="February 15, 2004 - February 21, 2004" />
17 </head>
18 <body class="layout-one-column">
19    <div id="container">
20       <div id="container-inner" class="pkg">
21
22          <div id="banner">
23             <div id="banner-inner" class="pkg">
24                <h1 id="banner-header"><a href="http://defaria.com/blogs/Status/" accesskey="1">Status for Andrew DeFaria</a></h1>
25                <h2 id="banner-description">Searchable status reports and work log</h2>
26             </div>
27          </div>
28
29          <div id="pagebody">
30             <div id="pagebody-inner" class="pkg">
31                <div id="alpha">
32                   <div id="alpha-inner" class="pkg">
33                      
34                      <p class="content-nav">
35                         <a href="http://defaria.com/blogs/Status/archives/week_2004_02_01.html">&laquo; February  1, 2004 - February  7, 2004</a> |
36                         <a href="http://defaria.com/blogs/Status/">Main</a>
37                         | <a href="http://defaria.com/blogs/Status/archives/week_2004_02_15.html">February 15, 2004 - February 21, 2004 &raquo;</a>
38                      </p>
39                      
40                      
41                      
42
43                      <h2 class="date-header">February 13, 2004</h2>
44                      <a id="a000136"></a>
45                      <div class="entry" id="entry-136">
46                         <h3 class="entry-header">2.3.0.4 and more testing</h3>
47                         <div class="entry-content">
48                            <div class="entry-body">
49                               <p>Was trying to get all of my WebSAM testing completed but was not able to. Got kicked onto another test system and that one had problems. Luckily Asad and Jeff helped fix things up for me. Got a lot done but may need to do more tomorrow.</p>
50
51 <h3>2.3.0.4 releaseed</h3>
52
53 <p>2.3.0.4 bring in the FX branch into the 2.3 release line. It also has fairly major functionality identified by bug ID 3605 (287 elements changed!) and a new card, onu2311.</p>
54
55 <p>Please let me know when you guys and gals make a new card! While updating the makefile will indeed insure that the new card is build when one types make, I use scripts and processes that rely on the definition of <i>cards</i> defined in /Tools/adm/etc/cards and need to update that file when a new card appears. Thanks.</p>
56
57 <p>Regarding the FX branch: The FX branch was a temporary branch for engineers to work on until 2.3 stablized. As such, with it's successful merge I plan on <font color="red"><b>destroying</b></font> both us_fx and china_fx branches. A destroy means that <i>the branch, element versions on that branches,  any labels on those element versions and merge arrows to and from the FX branches will <b>disappear</b></i>. It will be as if suddenly a bunch of new FX related code got checked into the 2.3 release line. Since the FX branch was indeed temporary I don't see any problem with destroying it though. Let me know if you have any objection to this.</p>
58
59 <p>Before I destroy the FX branches however Hok has to check in his code and merge it to 2.4.</p>
60                               
61                               <p class="entry-footer">
62                                  <span class="post-footers">Posted by  at  8:57 PM</span> <span class="separator">|</span> <a class="permalink" href="http://defaria.com/blogs/Status/archives/000136.html">Permalink</a>
63                                  
64                                  
65                               </p>
66                            </div>
67                         </div>
68                      </div>
69                      
70                      
71
72                      <h2 class="date-header">February 12, 2004</h2>
73                      <a id="a000131"></a>
74                      <div class="entry" id="entry-131">
75                         <h3 class="entry-header">Trigger bug, Testing, FX Merge complete!</h3>
76                         <div class="entry-content">
77                            <div class="entry-body">
78                               <ul>
79
80 <li>Fixed bug in CheckinPostop.pl trigger. Seems we need to have a total of 4, count 'em, 4 "\" to equate to one "\" in Windows. Needed to change code to use "@\\\\salira" to indicate the salira vob.</li>
81
82 <li>Performed more testing of WebSAM. Didn't get very far because I encountered some sort of hardware problem that Asad got me out of (partitially). Still seem to have some misbehaving cards. Don't seem to have a PTC card in this system nor any ONUs. Must look into this more tomorrow.</li>
83
84 <li>Fixed bug in trigger for real this tiem. It was not as indicated above. We did not need extra "\"'s rather we needed to remove the "2> /dev/null" redirection as that is a Unix'ism and ActiveState Perl, which is the Perl the Clearcase is invoking, doesn't like that syntax!</li>
85
86 <li>Completed the FX merge!</li>
87
88 </ul>
89                               
90                               <p class="entry-footer">
91                                  <span class="post-footers">Posted by  at  5:34 PM</span> <span class="separator">|</span> <a class="permalink" href="http://defaria.com/blogs/Status/archives/000131.html">Permalink</a>
92                                  
93                                  
94                               </p>
95                            </div>
96                         </div>
97                      </div>
98                      
99                      
100
101                      <h2 class="date-header">February 10, 2004</h2>
102                      <a id="a000130"></a>
103                      <div class="entry" id="entry-130">
104                         <h3 class="entry-header">Fixing code</h3>
105                         <div class="entry-content">
106                            <div class="entry-body">
107                               <ul>
108
109 <li>Fixed bug in build script that incorrectly passes status back up to calling script. This caused build to report success when build actually failed</li>
110
111 <li>Fixed CheckInPostop script to check to see if label already exists instead of creating it everytime. This should reduce some nonsense error messages</li>
112
113 </ul>
114                               
115                               <p class="entry-footer">
116                                  <span class="post-footers">Posted by  at  4:55 PM</span> <span class="separator">|</span> <a class="permalink" href="http://defaria.com/blogs/Status/archives/000130.html">Permalink</a>
117                                  
118                                  
119                               </p>
120                            </div>
121                         </div>
122                      </div>
123                      
124                      
125
126                      <h2 class="date-header">February  9, 2004</h2>
127                      <a id="a000129"></a>
128                      <div class="entry" id="entry-129">
129                         <h3 class="entry-header">2.3.0.3 built - build bug</h3>
130                         <div class="entry-content">
131                            <div class="entry-body">
132                               <p>Built 2.3.0.3. Not sure if it's officially done yet in that there may be some problems with the ONU2310 FPGA image.</p>
133
134 <p>Meantime I've been trying to figure out why sometimes the build process says all is OK when there are build errors. Turns out to be a shell problem with tee. When building I'm doing:</p>
135
136 <pre>
137 $ make $card.sf 2>&1 | tee -a $teefile > $card.build.log
138 </pre>
139
140 <p>Seems this tee thing messes up the return code from make. This can be demonstrated simply by:</p>
141
142 <pre>
143 $ ls nonexistance_file 2>&1 | tee -a /tmp/ls.log > /tmp/ls2.log; echo $?
144 0
145 </pre>
146
147 <p>Need to figure out how to fix this...</p>
148
149 <p>Merged NeoPON.ccp from 2.2 -> 2.3 by drawing merge arrow. This was after Zhiyi OKed this merge.</p>
150
151 <p>Worked out remaining merge issues on other branches. These were largely "can't check in identical file" type problems.</p>
152
153 <p>Attempted an FX -> 2.3 merge. Only like 40 elements to merge but some manual merging was required. Due to 2.3.0.3 build for KDDI this was put on hold. Need to merge this then allow Hok to check in before destroying this branch.</p>
154                               
155                               <p class="entry-footer">
156                                  <span class="post-footers">Posted by  at  5:37 PM</span> <span class="separator">|</span> <a class="permalink" href="http://defaria.com/blogs/Status/archives/000129.html">Permalink</a>
157                                  
158                                  
159                               </p>
160                            </div>
161                         </div>
162                      </div>
163                      
164                   </div>
165                </div>
166             </div>
167          </div>
168       </div>
169    </div>
170 </body>
171 </html>