Logging (reporting) |

Automatic test results logging (reporting) Test events (such as errors) are always automatically logged to the Event log history. This can be viewed by selecting the "Event Log" tab on the main window. This type of logging is not affected by the “Logging on” option, which refers to automatic logging to disk. Text and HTML reports can be manually created using “File”, "Save report”. This will save System information, a result summary and the recent Detailed Event log history. A customer style HTML test certificate is also available. Note: Text files are stored in UNICODE (not ASCII) which allows for the consistent encoding, representation and handling of text expressed in most of the world's writing systems. Turn automatic logging on Logging to disk is switched on and off with the “Turn automatic 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 files will be created when a test run starts. The log files are closed and available for use by another application when "Turn automatic logging on" is switched off, any of the logging options (Log Directory, Detail Level, Text/HTML Format) are changed, or when BurnInTest is exited or automatically stopped with a REBOOT or REBOOTEND scripting command. Log file name Log file name The Log file name allows the directory and filename prefix to be specified. For the default of “Time stamped files”, 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. Log name prefix Specify a “Log name prefix” if you wish to prefix the standard BurnInTest Text or HTML log filenames with some text. For example, if you want to prefix the standard BurnInTest log filenames with the text “SPECIAL_TEST_” then just enter, SPECIAL_TEST_ This prefix to the log file name can use Windows environment variables, such as %COMPUTERNAME%, %USERNAME%, %OS%, %PROCESSOR_ARCHITECTURE%. So, if for example you wanted to prefix log files with a test run description, the computer’s name and the user’s name, just enter, %COMPUTERNAME%_%USERNAME%_ There is a special BurnInTest variable, "%REPORTSERIAL%", that can be used in the Log file prefix field. This text will be replaced with the serial number as saved in the report information. This will only occur if %REPORTSERIAL% has not already been expanded by an existing Windows environment variable (as above). Any invalid filename characters (\ / : * ? " < > |) that are part of the serial will be replaced with "-" characters. Time stamped files / Single file By default, time stamped log files are created, this is the “Time stamped files” option. A new set of log files will be created when Logging On is switched on, any of the logging options (Log Directory, Detail Level, Text/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. By specifying “Single file”, no date or time stamp is appended to the filename and only a single log file (and if specified, a single trace file) will be created and all results will be logged to this file. “Single file” may be a useful option when the output is to be processed by an external program. Notes: 1) When running BurnInTest from a USB drive, using the -p command line parameter, it is recommended that you do not specify a Log file path, only a file name. By doing this, if the USB drive letter changes between systems then the Log file will still be stored in the BurnInTest directory on the USB drive. 2) Unlike V5 of BurnInTest, you can specify any environment variable in the log name prefix. As such, you need to be careful in regards to the environment variable you use. For example, don't specify an environment variable that contains a directory path, as this may be invalid. Report types The format of the Result summary and Normal log files may be specified to be either text and/or HTML via the “Text”, “HTML” or "Customer certificate" buttons. This setting will also determine the format of the Trace logs. A statistics report can also be selected to log test monitoring data in a CSV (Comma Separated Variable) format for post test analysis. Currently this includes data logging for temperature, fans* and voltage* when selected in Preferences->Temperature. The interval of logging is specified in Preferences->Temperature. The statistics log file name and other logging characteristics are specified as per other log files, and will contain the suffix _temp.csv. *3rd party HMonitor or SpeedFan software is required to monitor fans and voltage. Report detail Log file detail level A “Log file 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 (e.g. 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).
Trace file detail level A “Trace file detail 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, a summary of test activities (e.g. The starting and stopping of tests) and some additional error descriptions. Includes a description of the current test configuration.
3. | Activity trace level 2. Produces a .trace file with the “Activity Trace level 1” information and a detailed description of the test activity.
Summarize Some test runs can lead to a large number of error events that are the same. To produce a summarized log of these errors, select “Summarize”. When more than 3 events that are the same are produced in chronological order, the 3rd event through to the last same event will be summarized into a single line, together with an indication of the number of events that are the same that have not been displayed. The default is to not summarize events. Max file size (lines) Setting “Max file size” specifies the approximate maximum file size in terms of the number of lines in either the log or trace files. 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. It will also log temperature and battery values if these options are selected. 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
When using BurnInTest Scripting, accumulating test results is useful to accumulate results across multiple tests runs (i.e. multiple RUN commands). Accumulate test results is the typical settings for scripting multiple test runs in a single script file. Accumulated results will be cleared at the start of each test script and the accumulation occurs across all test runs within that script. Test results can also be cleared using the ‘Edit / Clear All Results’ menu item. See also Example reports Calling external programs via Auto stop actions Maintaining multiple test configurations