@@ -2074,11 +2074,11 @@
A: post config processing
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?
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!
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.
- - | -This technique can be very helpful in debugging running of EDA tools in Perl, Ruby, Python or tcl scripts: | -
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:
some_code(); $cmdline="virtuoso -some-switches and params ..."; @@ -2207,27 +2201,37 @@In scripts just insert the commands, this example helps you identify if "some commands …" changed any environment variables.:
myscript.sh-env > somefile-before.log +env | sort > somefile-before.log some commands ... -env > somefile-after.log+env | sort > somefile-after.log-Use meld to examine the differencesmeld somefile-before.log somefile-after.log-Start an xterm to examine the environment, run scripts etc:
+In a config file:
To try various values for a variable without mutating the current value
SOMEVAR=123 runcmd.sh+
#{shell xterm} (this blocks)+
(setenv SOMEVAR 123;runcmd.sh) + +# OR + +env SOMEVAR=123 runcmd.sh
Similarly in a script just call the xterm.