Logging Preferences |
Top Previous Next |
Logging to the Detailed Error log history Errors are automatically logged to the Detailed Error log history. This log is viewed using “View”, ”Error Log File”. This type of logging is not affected by the “Logging on” option, which refers to automatic disk logging. Note: Text and HTML disk logs can be manually created using “File”, "Save test log”. This will save System information, a result summary and the recent Detailed Error log history (up to 1000 entries).
Automatic disk logging Logging to disk is switched on and off with the “Logging on” option. When disk logging is on, BurnInTest will log System information, results, result summaries, and detailed error descriptions to files based on the following user settings.
The log directory allows the directory and filename prefix to be specified. The file will automatically be appended with _YYMMDD_HHMMSS.log, .htm or .trace, specifying the Year, Month, Day, Hour, Minute & second that the disk log file was created.
A “Log detail level” may be selected for disk logging to specify the amount of information to be written to disk. The options that may be selected are:
A “Trace level” may be selected for detailed disk logging to specify the amount of information to be written to disk. The options that may be selected are:
Setting “Max file size” specifies the approximate maximum file size in terms of the number of lines in either the log or trace files.
The format of the Result summary and Normal log files may be specified to be either ASCII text or HTML via the “ACSII Format” or “HTML Format” buttons. Trace logs are always in ASCII text.
A new set of log files will be created when Logging On is switched on, any of the logging options (Log Directory, Detail Level, ASCII/HTML Format) are changed, or when BurnInTest is started with Logging switched on. The only exception is when BurnInTest is automatically stopped with a REBOOT or REBOOTEND scripting command, and then the original log files will be re-opened and appended to.
The log files are closed and available for use by another application when Logging On is switched off, any of the logging options (Log Directory, Detail Level, ASCII/HTML Format) are changed, or when BurnInTest is exited or automatically stopped with a REBOOT or REBOOTEND scripting command.
Log Name Prefixing (Text/HTML) If you wish to prefix the standard BurnInTest Text or HTML log filenames you can type a prefix string into the “Prefix” edit box. For example, if you want to prefix the standard BurnInTest log filenames with the text “SPECIAL_TEST_” then just enter, SPECIAL_TEST_
Log Clearing Two options are available for clearing log files and result files. Logs can either be cleared each time a new test run is started or results can be accumulated across several test runs. The accumulate option is useful when doing reboot testing. Once the accumulate option has been set the only way result and log files can be cleared is with the ‘Edit / Clear All Results’ menu item. Having the accumulate option set means that the error count, cycle count and operations count values are the total values that have been accumulated across all test runs on this machine. Accumulation will also occur across scripted reboots, sleeps and execute commands. Note: Regardless of the configuration settings, the detailed error and status log history is maintained at a maximum of 1000 lines, with the oldest data cleared if this size is exceeded.
See also Calling external programs via Auto stop actions (see § 4.6 “Timer and test duration preferences” p.23). Maintaining multiple test configurations (see § 8.1 “Maintaining multiple test configurations” p.35).
|