001
002 /************************************************/
003 /* */
004 /* EXPERT CORNER */
005 /* */
006 /* */
007 /* (If you don't want to change the way that) */
008 /* (messages are displayed, rather you just ) */
009 /* (want to edit messages, then skip down to) */
010 /* (the USER CORNER ) */
011 /* */
012 /************************************************/
013
014 var messages = new Array();
015
016 /******************************************/
017 /* A crappy Javascript class for messages */
018 /******************************************/
019
020 function Message(date,text,isImportant){
021 this.theDate = date;
022 this.theText = text;
023 this.isImportant = isImportant;
024 messages.push(this);
025 }
026
027 /***************************************************/
028 /* Functions to do with displaying on the web page */
029 /***************************************************/
030
031 /* Display style for the message text */
032 function textStyle(isImportant){
033 style = 'font-family:arial;font-size:10pt;';
034 if (isImportant){
035 style = style + 'font-weight:bold;color:red';
036 }
037 else{
038 style = style + 'color:black';
039 }
040
041 return style;
042 }
043
044 /* Display style for the date*/
045 function dateStyle(){
046 return 'font-family:arial;font-size:10pt;color:black;font-weight:bold';
047 }
048
049 function titleStyle(){
050 return 'font-family:sans-serif;font-weight:bold;font-size:10pt;color:#88f;background-color:#ccf';
051 }
052
053 /* HTML code for displaying a message*/
054 function display(numbMessagesToDisplay,title){
055 htmlCode = '<div align="center">';
056 htmlCode += '<table width="100%" border="0" cellspacing="0" cellpadding="0" bgcolor="#dddddd">';
057 htmlCode += '<tr><td colspan= "4" align="center" style="' + titleStyle() + '">' + title + '</td></tr>'
058
059 for (var i=messages.length-1;i >= (messages.length - numbMessagesToDisplay);i--){
060 message = messages[i];
061 htmlCode += '<tr style="' + dateStyle() + '">';
062 htmlCode += '<td>' + message.theDate + '</td>';
063 htmlCode += '</tr>';
064 htmlCode += '<tr style="' + textStyle(message.isImportant) + '">';
065 htmlCode += '<td>' + message.theText + '</td>';
066 htmlCode += '</tr>';
067 }
068
069 htmlCode += '</table>';
070 htmlCode += '</div>';
071
072 document.write(htmlCode);
073
074 }
075
076 /************************************************/
077 /* */
078 /* USER CORNER */
079 /* */
080 /* */
081 /************************************************/
082
083 new Message('27th February 2007','We currently run SLC3 and SLC4 (32 bit) AFS dev nightlies. Things to note:<ul><li>rel_2: SLC4_32 platform available for checking</li><li>rel_3: SLC3 platform available for checking</li><li>rel_4: RTT run, but low quality build.</li><li>rel_0/1/4/5/6: both platforms available for checking</li></ul>',false);
084
085 new Message('1st March 2007','Today\'s rel_4 runs have completed successfully. Problems identified with yesterday\'s SLC4 rel_3 run:<ul><li>Run manually shutdown: 8 InDetRTT jobs affected. Cause: Batch system did not return these jobs.</li></ul>',false);
086
087 new Message('2nd March 2007','The JOBOPTIONSSEARCHPATH env var has changed format in today\'s rel_5 compared to yesterday. The RTT runs have been delayed while we adapted our code. SLC4 has now completed. SLC3 ongoing.',false);
088
089 new Message('3rd March 2007','Today\'s rel_6 SLC4 run complete. SLC3 run starts at 13:00. Yesterday\'s SLC3 run did not shut down correctly, but all packages completed.',false);
090
091 new Message('5th March 2007','Problems with SLC3 runs since Friday. Investigation ongoing.',false);
092
093 new Message('6th March 2007','Yesterday\'s rel_1 SLC3 build has been re-run and is complete. Will re-run rel_0 SLC3 shortly. 12.0.6 run seems to have been killed (probably by the network problems) before completion. Is re-running now.<br /><b>Note: RTT pilot jobs have been switched off for the past few days. Hence total number of jobs has dropped considerably.</b>',false);
094
095 new Message('7th March 2007','rel_0 has been re-run. 12.0.6 is essentially done (there are a couple of jobs stuck on the batch system apparently). Today\'s rel_3 SLC4 run has almost completed.',false);
096
097 new Message('8th March 2007','Today\'s rel_4 SLC4 had problems due to planned IT network intervention. Re-running. No SLC3 build was available yesterday. None will be available today (SLC3 build machines down).',false);
098
099 new Message('9th March 2007','Today\'s rel_5 SLC4 is running. No SLC3 run available yet. None for past 2 days.',false);
100
101 new Message('10th March 2007','Today\'s rel_6 SLC4 has run except for one long queue job. No SLC3 run available yet.',false);
102
103 new Message('12th March 2007','Today\'s rel_1 SLC4 has run. No SLC3 run available yet.',false);
104
105 new Message('13th March 2007','Today\'s rel_2 SLC4 has run. SLC3 build is running.',false);
106
107 new Message('14th March 2007','Today\'s SLC4 run accidentally terminated. Re-running.',false);
108
109 new Message('16th March 2007','Today\'s SLC4 rel_5 run ongoing.',false);
110
111 new Message('18th March 2007','Problems with these web pages being addressed.',true);
112
113 new Message('19th March 2007','Web pages accessible again. Previous tag back into production for now, rel_1 SLC4 ongoing.',false);
114
115 new Message('20th March 2007','rel_2 SLC4 done. SLC3 ongoing.',false);
116
117 new Message('21st March 2007','This morning\'s SLC4 run has just started. The current tag remains in production for now.',false);
118
119 new Message('22nd March 2007','This morning\'s rel_4 SLC4 run is complete. No SLC3 build yet available.',false);
120
121 new Message('25th March 2007','This morning\'s rel_0 SLC4 run is proceeding very slowly.',false);
122
123 new Message('26th March 2007','This morning\'s rel_1 dev SLC4 run postponed to allow running of val SLC4 nightly.',false);
124
125 new Message('27th March 2007','This morning\'s rel_2 val SLC4 run ongoing. SLC4 dev rel_2 starts 13:00.',false);
126
127 new Message('2nd April 2007','This morning\'s rel_1 val SLC4 run ongoing. SLC4 dev rel_1 starts 13:00.',false);
128
129 new Message('5th April 2007','This morning\'s rel_3 SLC4 bugfix run complete (44/243 jobs OK). rel_3 val starts 12:00; rel_3 SLC3 bugfix at 18:00.',false);
130
131 new Message('6th April 2007','This morning\'s rel_5 SLC4 bugfix AFS build is not yet available.',false);
132
133 new Message('9th April 2007','There was no rel_0 SLC3 bugfix build available yesterday. SLC4 was available, and was run (as was the val nightly)',false);
134
135 new Message('9th April 2007','Batch queues have been inactivated (by an administrator, not us). Consequently no RTT runs are making progress.',true);
136
137 new Message('10th April 2007','Batch queues appear normal again. This problem resulted in:<ul><li>Yesterday\'s rel_1 bugfix SLC3 build not run</li><li>Majority of jobs in rel_1 val/bugfix SLC4 build timed out.</li></ul>',true);
138
139 new Message('11th April 2007','rel_3 SLC4 bugfix done. val build ongoing (not yet web visible).',false);
140
141 new Message('12th April 2007','rel_4 SLC4 bugfix done. val build ongoing.',false);
142
143 new Message('13th April 2007','rel_5 SLC4 bugfix and val runs ongoing.',false);
144
145 new Message('14th April 2007','rel_6 SLC4 bugfix is complete, but should be ignored. The NICOS-produced flag that the RTT team was told could be used as a reliable indication that the release was ready appears, today, to have been set before all projects were truly available. The RTT thus processed an incomplete build.', true);
146
147 new Message('17th April 2007','The machine on which RTT production runs are launched was switched off by IT a couple of days ago due to problems. It is still off, and so we have switched to the only other machine available to us. Unfortunately that machine appears sluggish so we have not yet been able to launch an RTT run.',false);
148
149 new Message('17th April 2007','We are currently running yesterday\'s rel_1 SLC4 bugfix.',false);
150
151 new Message('18th April 2007','Our main RTT production machine remains down whilst IT investigate. A second production machine to which we switched was rebooted last night whilst we were running yesterday\'s rel_2 SLC4 bugfix. The run was of course killed. We are currently re-running it but it will be stopped shortly to allow us to put in place RunTimeTester-00-01-85. When in place, we\'ll start up today\'s rel_3 val build.',false);
152
153 new Message('18th April 2007','The ongoing run of yesterday\'s rel_2 SLC4 bugfix build has been halted. Today\'s rel_3 val build launches at 18:30 (using new tag RunTimeTester-00-01-85).',false);
154
155 new Message('18th April 2007','Today\'s rel_3 val is almost done. SLC3 bugfix ongoing.',false);
156
157 new Message('19th April 2007','Yesterday\'s ongoing rel_3 SLC3 bugfix and val runs were killed for reasons not understood. Today\'s rel_4 SLC4 bugfix build is done and available. rel_4 val is ongoing. If available, rel_4 SLC3 bugfix will launch tonight.',false);
158
159 new Message('20th April 2007','<ul><li>Today\'s rel_5 SLC4 bugfix run ongoing.</li><li>Yesterday\'s rel_4 val run closed down with loss of 6 jobs (G4AtlasApps/JetRec packages). Why? Machine was under heavy stress and SLC3 bugfix run was starting up. 2 ongoing runs would have probably crashed the machine.</li></ul>',false);
160
161 new Message('20th April 2007','Today\'s rel_5 SLC4 bugfix is done. val run launches at 14:20.',false);
162
163 new Message('20th April 2007','Today\'s rel_5 SLC4 bugfix is done. val run finished, but is being launched again: batch system failed to return ~70 job logs.',false);
164
165 new Message('20th April 2007','No rel_5 SLC3 bugfix build today.',false);
166
167 new Message('23rd April 2007','Yesterday\'s bugfix and today\'s SLC4 bugfix runs should be ignored: AFS build was bad. Edit: This morning\'s SLC4 bugfix has been fixed, and so will be re-run.',false);
168
169 new Message('23rd April 2007','Over the weekend RTT runs were ongoing, but failed to appear on the web pages. The pages will be manually updated shortly to make visible these results. <b>Edit: DONE. rel_1 SLC4 bugfix ongoing.</b>', false);
170
171 new Message('24th April 2007','No rel_1 val build available yesterday. No rel_2 builds available so far today.',false);
172
173 new Message('25th April 2007','No rel_2 bugfix SLC3 build available yesterday. Today\'s rel_3 bugfix almost done. val nightly to be re-run following fix to the build.',false);
174
175 new Message('26th April 2007','Today\'s rel_4 val run ongoing. No bugfix builds available yet.', false);
176
177 new Message('27th April 2007','No builds available yet.', false);
178
179 new Message('30th April 2007','Since Friday the flag set by NICOS and used by the RTT to indicate that a given build is ready, has not been set. The RTT did not run any builds, except for yesterday\'s rel_0 val, for which the flag was set manually by Alex (thanks!).', true);
180
181 new Message('30th April 2007','Today\'s rel_1 SLC4 bugfix almost done. val nightly ongoing.', false);
182
183 new Message('2nd May 2007','Today\'s rel_3 val nightly is launching soon. No bugfix builds available yet.', false);
184
185 new Message('4th May 2007','Today\'s rel_5 val ongoing; but build looks corrupt.', false);
186
187 new Message('5th May 2007','Today\'s rel_6 val run launches at 11:00.', false);
188
189 new Message('5th May 2007','Today\'s rel_6 val run ongoing.', false);
190
191 new Message('7th May 2007','Disk quota exceeded over the weekend. Both rel_6 bugfix runs affected: 2-3 jobs (CaloRecEx/egammaRec) not completed.', false);
192
193 new Message('8th May 2007','Today\'s rel_2 SLC4 bugfix and val runs are ongoing.', false);
194
195 new Message('8th May 2007','All today\'s rel_2 runs complete (in all runs, some jobs from CaloRecEx/egammaRec got stuck in batch and were aborted manually).', false);
196
197 new Message('13th May 2007','There was no rel_6 val build available yesterday.', false);
198
199 new Message('16th May 2007','The empty "Project" column below (if you are on the start page with the list of available RTT runs) will gradually be filled.', false);
200
201 new Message('7th June 2007','<h2>Here is the only working link to <a target="main_frame" href="http://cern.ch/atlasrtt/13.0.10/build/i686-slc4-gcc34-opt/offline/page2.xml">13.0.10 results</a>.</h2>', true);
202
203 new Message('18th June 2007','<h2>There are problems with RTT cluster. Because of these, there were no runs yesterday 17th and none this morning.Please check RTT hypernews forum for updates.</h2>', true);
204
205 new Message('20th June 2007','<h3>RTT running has resumed.</h3>', false);
206
207 new Message('21st June 2007','<ul><li><h2>Here is the only working link to <a target="main_frame" href="http://cern.ch/atlasrtt/13.0.10/build/i686-slc4-gcc34-opt/offline/page2.xml">13.0.10 results</a>.</h2></li></ul>', true);
208
209 new Message('6th June 2007','<ul><li><h2>Here are the only working links to <a href="http://cern.ch/atlasrtt/page1.php?xml=13.0.10/build/i686-slc4-gcc34-opt/offline/RTTSummary.xml&viewBy=package">13.0.10 results</a> and <a href="http://cern.ch/atlasrtt/page1.php?xml=13.0.20/build/i686-slc4-gcc34-opt/offline/RTTSummary.xml&viewBy=package">13.0.20 results</a>.</h2></li></ul>', true);
210
211 /***********************************************************/
212 /* ADDING A NEW MESSAGE */
213 /***********************************************************/
214 /* Add your latest message above this comment box */
215 /* Skeleton code is: */
216 /* new Message('theDate','theMessage',false); */
217 /* */
218 /* where false means the message gets displayed normal */
219 /* true means message displayed in red and bold */
220 /***********************************************************/
221
222 /* Show the last how many messages ? */
223 display(numberOfMessagesToDisplay = 1,title=":: Message of the Day ::");
| Due to the LXR bug, the updates fail sometimes to remove references to deleted files. The Saturday's full rebuilds fix these problems |
|
This page was automatically generated by the
LXR engine.
|
|