Event Log |

The detailed event log history can be opened from the ‘Event Log ’ tab on the main window. It contains a record of recent errors and status messages that have occurred during a test run. It is possible to save a copy of this log of recent history using the ‘File -> Save Report’ menu item.

The log can contain up to 1000 messages. After 1000, the oldest messages are overwritten by the newer ones. The log window is updated in real time and can left open while a test run is in progress.

Error Classification

Where logging records an error, the severity of this error (CRITICAL, SERIOUS, WARNING or INFORMATION) is logged. Where an informational line (related to this error) follows the error line, the error classification is not repeated (to aid determination of the number of unique errors per classification).

Each line is color coded based on the Error Classification.

Time stamp

The time stamp records the time when the event occurred. The format is, YYYY-MM-DD HH:MM:SS

Test type

The test type refers to the name of the test which originated the event. Examples are, “RAM”, Floppy Disk”. The word “Status”, indicated that the event is not an error but just a status message.

Details

This is a text field that contains additional information about the error (or status message).

In some cases a log entry may be spread across two lines. The 1st line will contain some general information about the error and the 2nd line will contain more detail.

Some error messages may contain internal program variables (and thus be fair cryptic). These are not always intended to be interpreted by the user can but help us track down faults in our software.

Configuring Error Classifications

Each of the standard errors detected by BurnInTest can configured to include a customer specific string and error classification. The file BITErrorClassification.txt (in the software directory) contains the error text and classification used by BurnInTest.

The file is formatted as a Comma Separated File with four fields:

1. | Error number – this must not be changed by the customer;

2. | Error description text – this may be changed. This must be a sting enclosed by quotes;

3. | Error classification – this may be changed. This must be one of the following text values (not in quotes):

CRITICAL, SERIOUS, WARNING, or INFORMATION

A number of errors may be configured to be ignored (not reported as errors), as they may be considered ‘below the radar’. These are configured by setting the Error classification to NONE. These are:

• | 138,"Warning: Could not lock parallel port",WARNING,PP

• | 146,"Frame could not be displayed and was skipped",INFORMATION,

• | 160,"Butterfly seeking test not supported for this disk",INFORMATION,

• | 182,"Video Playback is dropping samples",WARNING,

• | 184,"External Plug-in reported error",WARNING,

• | 187,"Unable to communicate with the External Plug-in",WARNING,

• | 198,"Data packet transmission error recovery to be attempted",WARNING,

• | 199,"Data packet reception error recovery to be attempted",WARNING,

Other errors may not be configured to be ignored in this way.

1. | Customer comment – this is optional and may be changed – it is ignored by BurnInTest.

Comment lines may be inserted by using a “#” at the start of the line. These lines will be ignored by BurnInTest.

An example is shown below:

# PassMark BurnInTest,,,

# Error message text and classification,,,

0,"No errors",NONE,

1,"Incorrect mathematical addition",SERIOUS,

2,"Incorrect mathematical subtraction",SERIOUS,

3,"Incorrect mathematical division",SERIOUS,

4,"Incorrect mathematical multiply",SERIOUS,

5,"Incorrect MMX addition",SERIOUS,

6,"Incorrect MMX subtraction",SERIOUS,

7,"Incorrect MMX multiplication",SERIOUS,

8,"Failed Windows call - Line Drawing",SERIOUS,