Megatest

Check-in [4a356a51e5]
Login
Overview
Comment:Updated the documentation
Downloads: Tarball | ZIP archive | SQL archive
Timelines: family | ancestors | descendants | both | trunk
Files: files | file ages | folders
SHA1: 4a356a51e5d0897a28dd7697859129c28adfe768
User & Date: matt on 2011-05-16 23:59:36
Other Links: manifest | tags
Context
2011-05-17
00:50
Updated the documentation check-in: a526d7ade5 user: matt tags: trunk
2011-05-16
23:59
Updated the documentation check-in: 4a356a51e5 user: matt tags: trunk
23:50
Updated the documentation check-in: 895455e988 user: matt tags: trunk
Changes

Modified docs/megatest.html from [aa66bfa737] to [342589359c].

216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280



281
282
283
284
285
286
287
<h2 class="Section">
<a class="toc" name="toc-Section-2.2">2.2</a> Setup
</h2>
<h3 class="Subsection">
<a class="toc" name="toc-Subsection-2.2.1">2.2.1</a> Create megatest.config
</h3>
<div class="Unindented">
Create the file megatest.config using the megatest.config template from the tests directory. At a minimum you need the following:
</div>
<div class="Code">
# Fields are the keys under which your test runs are organized
</div>
<div class="Code">
[fields]
</div>
<div class="Code">
field1 TEXT
</div>
<div class="Code">
field2 TEXT
</div>
<div class="Code">

</div>
<div class="Code">
[jobtools]
</div>
<div class="Code">
# The launcher launches jobs to the local or remote hosts,
</div>
<div class="Code">
# the job is managed on the target host by megatest,
</div>
<div class="Code">
# comment out launcher to run local only. An example launcher
</div>
<div class="Code">
# "nbfake" can be found in the utils directory. 
</div>
<div class="Code">
launcher nbfake
</div>
<div class="Code">

</div>
<div class="Code">
# The disks section specifies where the tests will be run. As you
</div>
<div class="Code">
# run out of space in a partition you can add additional disks
</div>
<div class="Code">
# entries.
</div>
<div class="Code">
# Format is:
</div>
<div class="Code">
# name /path/to/area 
</div>
<div class="Code">
[disks]
</div>
<div class="Code">
1 /tmp 



</div>
<h3 class="Subsection">
<a class="toc" name="toc-Subsection-2.2.2">2.2.2</a> Create runconfigs.config
</h3>
<div class="Unindented">
This file is used to set environment variables that are run specific. You can simply create an empty file to start.<div class="listing">
<pre class="listing"># runconfigs.config







|
<
<
|
<
<

<
<

<
<

<
<
|
<
<

<
<

<
<

<
<

<
<

<
<

<
<
|
<
<

<
<

<
<

<
<

<
<

<
<

<
<

>
>
>







216
217
218
219
220
221
222
223


224


225


226


227


228


229


230


231


232


233


234


235


236


237


238


239


240


241


242
243
244
245
246
247
248
249
250
251
252
<h2 class="Section">
<a class="toc" name="toc-Section-2.2">2.2</a> Setup
</h2>
<h3 class="Subsection">
<a class="toc" name="toc-Subsection-2.2.1">2.2.1</a> Create megatest.config
</h3>
<div class="Unindented">
Create the file megatest.config using the megatest.config template from the tests directory. At a minimum you need the following:<div class="listing">


<pre class="listing"># Fields are the keys under which your test runs are organized


[fields]


field1 TEXT


field2 TEXT





[jobtools]


# The launcher launches jobs to the local or remote hosts,


# the job is managed on the target host by megatest,


# comment out launcher to run local only. An example launcher


# "nbfake" can be found in the utils directory. 


launcher nbfake





# The disks section specifies where the tests will be run. As you


# run out of space in a partition you can add additional disks


# entries.


# Format is:


# name /path/to/area 


[disks]


1 /tmp 
</pre>
</div>

</div>
<h3 class="Subsection">
<a class="toc" name="toc-Subsection-2.2.2">2.2.2</a> Create runconfigs.config
</h3>
<div class="Unindented">
This file is used to set environment variables that are run specific. You can simply create an empty file to start.<div class="listing">
<pre class="listing"># runconfigs.config
1409
1410
1411
1412
1413
1414
1415
1416
1417
1418
1419
1420

</table>

</div>

<hr class="footer"/>
<div class="footer" id="generated-by">
Document generated by <a href="http://elyxer.nongnu.org/">eLyXer 1.0.0 (2010-07-21)</a> on <span class="create-date">2011-05-16T22:49:35.164246</span>
</div>
</div>
</body>
</html>







|




1374
1375
1376
1377
1378
1379
1380
1381
1382
1383
1384
1385

</table>

</div>

<hr class="footer"/>
<div class="footer" id="generated-by">
Document generated by <a href="http://elyxer.nongnu.org/">eLyXer 1.0.0 (2010-07-21)</a> on <span class="create-date">2011-05-16T22:59:24.726050</span>
</div>
</div>
</body>
</html>

Modified docs/megatest.lyx from [98c122c376] to [902c5a499e].

173
174
175
176
177
178
179


180
181
182

183
184
185
186

187
188
189
190

191
192
193
194

195
196
197
198
199
200
201
202

203
204
205
206

207
208
209
210

211
212
213
214

215
216
217
218
219

220
221
222
223
224

225
226
227
228
229
230
231
232

233
234
235
236
237

238
239
240
241

242
243
244
245

246
247
248
249

250
251
252
253

254
255
256
257

258





259
260
261
262
263
264
265
Create megatest.config
\end_layout

\begin_layout Standard
Create the file megatest.config using the megatest.config template from the
 tests directory.
 At a minimum you need the following:


\end_layout

\begin_layout Code

# Fields are the keys under which your test runs are organized
\end_layout

\begin_layout Code

[fields]
\end_layout

\begin_layout Code

field1 TEXT
\end_layout

\begin_layout Code

field2 TEXT
\end_layout

\begin_layout Code

\end_layout

\begin_layout Code

[jobtools]
\end_layout

\begin_layout Code

# The launcher launches jobs to the local or remote hosts,
\end_layout

\begin_layout Code

# the job is managed on the target host by megatest,
\end_layout

\begin_layout Code

# comment out launcher to run local only.
 An example launcher
\end_layout

\begin_layout Code

# "nbfake" can be found in the utils directory.
 
\end_layout

\begin_layout Code

launcher nbfake
\end_layout

\begin_layout Code

\end_layout

\begin_layout Code

# The disks section specifies where the tests will be run.
 As you
\end_layout

\begin_layout Code

# run out of space in a partition you can add additional disks
\end_layout

\begin_layout Code

# entries.
\end_layout

\begin_layout Code

# Format is:
\end_layout

\begin_layout Code

# name /path/to/area 
\end_layout

\begin_layout Code

[disks]
\end_layout

\begin_layout Code

1 /tmp 





\end_layout

\begin_layout Subsection
Create runconfigs.config
\end_layout

\begin_layout Standard







>
>
|

|
>



|
>



|
>



|
>



|



|
>



|
>



|
>



|
>




|
>




|
>



|



|
>




|
>



|
>



|
>



|
>



|
>



|
>

>
>
>
>
>







173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
Create megatest.config
\end_layout

\begin_layout Standard
Create the file megatest.config using the megatest.config template from the
 tests directory.
 At a minimum you need the following:
\begin_inset listings
inline false
status open

\begin_layout Plain Layout

# Fields are the keys under which your test runs are organized
\end_layout

\begin_layout Plain Layout

[fields]
\end_layout

\begin_layout Plain Layout

field1 TEXT
\end_layout

\begin_layout Plain Layout

field2 TEXT
\end_layout

\begin_layout Plain Layout

\end_layout

\begin_layout Plain Layout

[jobtools]
\end_layout

\begin_layout Plain Layout

# The launcher launches jobs to the local or remote hosts,
\end_layout

\begin_layout Plain Layout

# the job is managed on the target host by megatest,
\end_layout

\begin_layout Plain Layout

# comment out launcher to run local only.
 An example launcher
\end_layout

\begin_layout Plain Layout

# "nbfake" can be found in the utils directory.
 
\end_layout

\begin_layout Plain Layout

launcher nbfake
\end_layout

\begin_layout Plain Layout

\end_layout

\begin_layout Plain Layout

# The disks section specifies where the tests will be run.
 As you
\end_layout

\begin_layout Plain Layout

# run out of space in a partition you can add additional disks
\end_layout

\begin_layout Plain Layout

# entries.
\end_layout

\begin_layout Plain Layout

# Format is:
\end_layout

\begin_layout Plain Layout

# name /path/to/area 
\end_layout

\begin_layout Plain Layout

[disks]
\end_layout

\begin_layout Plain Layout

1 /tmp 
\end_layout

\end_inset


\end_layout

\begin_layout Subsection
Create runconfigs.config
\end_layout

\begin_layout Standard