| Page Properties | ||||||||||||||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
...
- Visibility: Public
- Change Control: Stable
- Synopsis: A new option added to pbs_benchpress command to enable saving post analysis data on test case failure in PTL
- Details: To enable saving post analysis data on test case failure in PTL, new command line option will be introduced called '--post-analysis-data=<dir>' in pbs_benchpress command. By default PTL will not save any post analysis data in failure case. When enabled, PTL will store post analysis data on failure in given <dir> (if <dir> does not exits then PTL will create it, with 0755 permission and owner will be current user (i.e. user who invoked pbs_benchpress command)) in below format
<dir>/<test suite 1 name>/
<test case 1 name>/
logfile_<status>
PBS_<hostname>.tar.gz
...
<test case n name>/
logfile_<status>
PBS_<hostname>.tar.gz
...
<test suite n name>/
<test case 1 name>/
logfile_<status>
PBS_<hostname>.tar.gz
<test case 2 name>/
logfile_<status>
PBS_<hostname>.tar.gz
...
<test case n name>/
logfile_<status>
PBS_<hostname>.tar.gz
This post analysis data includes following data:- logfile_<status of test case>
- This file contains PTL logs of current test case for which post analysis data is being stored
- <status of test case> can be one of following:
- PASS
- SKIP
- FAIL
- ERROR
- TIMEDOUT
- Also in last line of this file will have time taken by current test case
- PBS_<hostname>.tar.gz
- This file is nothing but PBS diag saved by pbs_diag command with renamed as PBS_<hostname>.tar.gz from pbs_diag_yymmdd_hhmmss.tar.gz
- PTL will run pbs_diag with following options
- -f: for running pbs_diag in non-interactive mode
- -j <jobid1>,<jobid2>,...,<jobidn>: comma separated list of job ids (if any)
- -d 2: To save PBS logs for last two days
- 2 days because there might be chances that date can switch (like midnight) while PTL is running test
- Also PTL will run pbs_diag command with -g <path to core file> if all core files found in PBS_HOME directory
- The output of above command will be store in <core file name>.out
- After taking pbs_diag output for core file, core file will be deleted from PBS_HOME directory
- PTL will run pbs_diag with following options
- This file is nothing but PBS diag saved by pbs_diag command with renamed as PBS_<hostname>.tar.gz from pbs_diag_yymmdd_hhmmss.tar.gz
- logfile_<status of test case>
...
- Visibility: Public
- Change Control: Stable
- Synopsis: A new option added to pbs_benchpress command to override default value of max post analysis data threshold count while running testsuite
- Details: While running testsuite, if saving post analysis data is enabled then PTL will save post analysis data for failure case till saved data count reaches <count> for the testsuite, once number of saved data the testsuite exceeds <count> then PTL will stops saving data for any further failure for that testsuite with error message "Total number of saved post analysis data for this testsuite is exceeded max postdata threshold (<count>)". Default max postdata threshold will be 10. <count> should integer while overriding default value for max postdata threshold using this option, if <count> is not integer then PTL will bail out with error message "Invalid value for max-postdata-threshold, please provide integer". <count> should be less or equal to 'tc-failure-threshold', if <count> is greater than 'tc-failure-threshold' then PTL will bail out with error message "Value for max-postdata-threshold should be less or equal to 'tc-failure-threshold'". <count> == 0 will disable this threshold. This threshold is only applies when saving post analysis data is enabled (i.e --post-analysis-data)