108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
|
[jobtools]
launcher bsub
# if defined and not "no" flexi-launcher will bypass launcher unless there is no
# match.
flexi-launcher yes
------------------------
Tricks
------
This section is a compendium of a various useful tricks for debugging,
configuring and generally getting the most out of Megatest.
Limiting your running jobs
~~~~~~~~~~~~~~~~~~~~~~~~~~
The following example will limit a test in the jobgroup "group1" to no more than 10 tests simultaneously.
In your testconfig:
|
|
|
|
|
|
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
|
[jobtools]
launcher bsub
# if defined and not "no" flexi-launcher will bypass launcher unless there is no
# match.
flexi-launcher yes
------------------------
Tricks and Tips
---------------
This section is a collection of a various useful tricks for that
didn't quite fit elsewhere.
Limiting your running jobs
~~~~~~~~~~~~~~~~~~~~~~~~~~
The following example will limit a test in the jobgroup "group1" to no more than 10 tests simultaneously.
In your testconfig:
|
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
|
---------------
[jobgroups]
group1 10
custdes 4
---------------
Debugging Tricks
----------------
Examining The Environment
~~~~~~~~~~~~~~~~~~~~~~~~~
Test Control Panel - xterm
^^^^^^^^^^^^^^^^^^^^^^^^^^
From the dashboard click on a test PASS/FAIL button. This brings up a test control panel. Aproximately near the center left of the
window there is a button "Start Xterm". Push this to get an xterm with the full context and environment loaded for that test. You can run
scripts or ezsteps by copying from the testconfig (hint, load up the testconfig in a separate gvim or emacs window). This is the easiest way
to debug your tests.
During Config File Processing
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
It is often helpful to know the content of variables in various
contexts as Megatest does the actions needed to run your tests. A handy technique is to force the startup of an xterm in the context being examined.
For example, if an item list is not being generated as expected you
can inject the startup of an xterm as if it were an item:
.Original items table
-----------------
[items]
CELLNAME [system getcellname.sh]
-----------------
.Items table modified for debug
-----------------
[items]
DEBUG [system xterm]
CELLNAME [system getcellnames.sh]
-----------------
When this test is run an xterm will pop up. In that xterm the
environment is exactly that in which the script "getcellnames.sh"
would run. You can now debug the script to find out why it isn't
working as expected.
|
<
<
<
<
<
<
<
<
<
<
<
<
<
<
<
<
<
<
<
<
<
<
<
<
<
<
<
<
<
<
<
<
<
<
<
<
<
<
<
<
|
134
135
136
137
138
139
140
141
142
143
144
145
146
147
|
---------------
[jobgroups]
group1 10
custdes 4
---------------
Organising Your Tests and Tasks
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
The default location "tests" for storing tests can be extended by
adding to your tests-paths section.
|