160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
|
----------------------------------------------------------------------
include::megatest-test-stages.dot[]
----------------------------------------------------------------------
.How to check variable values and inspect logs at each stage
[width="80%",cols="<,2m,2m",frame="topbot",options="header"]
|======================
|Stage | How to inspect | Watch for
|A: post config processing | megatest -show-config -target your/target | #f (failed var processing)
|B: post runconfig | megatest -show-runconfig -target your/target | Add -debug 0,9 to see which file your settings come from
|C: processing testconfigs | inspect output from "megatest -run ..." | Messages indicating issues process configs, dependency problems
|D: process testconfig for test launch | inspect output from megatest runner | Zero items (items expansion yielded no items)
|E,F: launching test | start test xterm, look at mt_launch.log | Did your batch system accept the job? Has the job landed on a machine?
|G: starting test | look at your batch systems logs for the process | Did the megatest -execute process start and run?
|H,H1,H2: step exectution | look at <stepname>.log, <stepname>.html and your own internal logs | Do you have sufficiently tight logpro rules? You must always have a "required" rule!
|======================
Bisecting megatest.csh/sh
^^^^^^^^^^^^^^^^^^^^^^^^^
Sometimes finding the environment variable that is causing the problem
|
|
|
|
|
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
|
----------------------------------------------------------------------
include::megatest-test-stages.dot[]
----------------------------------------------------------------------
.How to check variable values and inspect logs at each stage
[width="80%",cols="<,2m,2m",frame="topbot",options="header"]
|======================
|Stage | How to inspect | Watch for or try ...
|A: post config processing | megatest -show-config -target your/target | #f (failed var processing)
|B: post runconfig | megatest -show-runconfig -target your/target | Add -debug 0,9 to see which file your settings come from
|C: processing testconfigs | inspect output from "megatest -run ..." | Messages indicating issues process configs, dependency problems
|D: process testconfig for test launch | inspect output from megatest runner | Zero items (items expansion yielded no items)
|E,F: launching test | start test xterm, look at mt_launch.log | Did your batch system accept the job? Has the job landed on a machine?
|G: starting test | look at your batch systems logs for the process | Did the megatest -execute process start and run? Extract the "megatest -execute ..." command and run it from your xterm.
|H,H1,H2: step exectution | look at <stepname>.log, <stepname>.html and your own internal logs | Do you have sufficiently tight logpro rules? You must always have a "required" rule!
|======================
Bisecting megatest.csh/sh
^^^^^^^^^^^^^^^^^^^^^^^^^
Sometimes finding the environment variable that is causing the problem
|
230
231
232
233
234
235
236
237
238
239
240
241
242
243
|
-----------------
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.
NOTE: This technique can be very helpful in debugging running of EDA tools in Perl, Ruby, Python or tcl scripts:
.Perl example
..............................
some_code();
$cmdline="virtuoso -some-switches and params ...";
print "$cmdline"; # print the command line so you can paste it into the xterm that pops up
|
>
|
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
|
-----------------
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.
Similarly in a script just call the xterm.
NOTE: This technique can be very helpful in debugging running of EDA tools in Perl, Ruby, Python or tcl scripts:
.Perl example
..............................
some_code();
$cmdline="virtuoso -some-switches and params ...";
print "$cmdline"; # print the command line so you can paste it into the xterm that pops up
|
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
|
...................
In scripts just insert the commands, this example helps you identify
if "some commands ..." changed any environment variables.:
.myscript.sh
..............................
env > somefile-before.log
some commands ...
env > somefile-after.log
..............................
.Use meld to examine the differences
..............................
meld somefile-before.log somefile-after.log
..............................
Start an xterm to examine the environment, run scripts etc:
In a config file:
.megatest.config, runconfigs.config and testconfig files
#{shell xterm} (this blocks)
Similarly in a script just call the xterm.
|
|
|
>
>
|
>
>
>
>
>
|
>
>
>
>
|
>
|
>
>
>
>
>
>
|
>
|
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
|
...................
In scripts just insert the commands, this example helps you identify
if "some commands ..." changed any environment variables.:
.myscript.sh
..............................
env | sort > somefile-before.log
some commands ...
env | sort > somefile-after.log
..............................
.Use meld to examine the differences
..............................
meld somefile-before.log somefile-after.log
..............................
Oneshot Modifying a Variable
^^^^^^^^^^^^^^^^^^^^^^^^^^^^
To try various values for a variable without mutating the current value
.within a bash shell
..............................
SOMEVAR=123 runcmd.sh
..............................
.within csh
..............................
(setenv SOMEVAR 123;runcmd.sh)
# OR
env SOMEVAR=123 runcmd.sh
..............................
Capturing output from a command
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
.Use the "script" utility
..............................
script -c "virtuoso -params and switches ..."
..............................
|