Logging Preferences

Automatic 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. This log can be viewed by clicking on the Event Log tab.

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:

1.Result Summary only. Produces a .log or .htm file containing system information, a summary of the tests run (eg. Which tests, the number of operations and errors per test) and a summary of the serious and critical errors during a test run (cleared at the end of a non-scripted test run or at the end of the script for a scripted test run).

2.Normal. Produces a .log or .htm file containing the “Result Summary only” information and detailed errors (1 or 2 lines per error).

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:

1.No Trace log. No trace log is produced.  This is the default setting.

2.Activity Trace level 1. Produces a .trace with the “Normal” information and a summary of test activities (eg. The starting and stopping of tests).

3.Activity trace level 2. Produces a .trace file with the “Activity Trace level 1” information and a detailed description of the test activity.

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.

Note: Text and HTML disk logs can be manually created using “File”, "Save results report". This will save System information, a result summary and the recent Detailed Error log history (up to 1000 entries).

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_.

Report type

The format of the Result summary and Normal log files may be specified to be either ASCII text or HTML via the “Text (ASCII)”, “HTML” or "Customer certificate" buttons. This setting will also determine the format of the Trace logs.

Periodically log result summary reports during a test

When logging is switched on, by default a result summary report will be logged at the end of a test run. Change this value if you would like to log interim results summary reports during the test (every X minutes).

This will log the number of operations, errors etc at that periodic point in time.

One use of this option is to help obtain information about the testing status of a system prior to a system crash on an unstable system. Note: All error events are written in real time, so the main use of this option will be if there are few errors occurring.

Pre-test logging options

Test results, including the detailed error and status log history, can either be cleared each time a new test run is started or test results can be accumulated across several test runs.

Accumulating test results 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.

Log files may be appended to the existing log file or a new log file created at the start of each test run.

Three options are available for clearing/accumulating test results and creating/appending log files. These options are:

•Clear test results and create a new log

•Clear test results and append to the existing log

•Accumulate test results and append to the existing log

Special Flags

Several special flags are available to be used in the logging path and filename;

%SYSTEMSERIAL% - This will be replaced with either the serial number as set in the Report Information and if this value has not been set, the system serial number as retrieved by the dmidecode tool. For example "\logs\BitLog_%SYSTEMSERIAL%" can become "\logs\BitLog_SN123456"

%DATE% - This will be replaced with the date in YYYMMDD format.