Bug? Plugin Event Log mixup.

[Ian (PassMark)]

The new build V5.1 1009 with this correction has been posted:
http://www.passmark.com/download/bit_download.htm

Best regards,
Ian

[Ian (PassMark)]

This is a bug where the error severity is updated after the log line is written out - and hence the severity for a log line is actually for the preceding log line. The error counts for the error classification view on the main window are correct however.

We will correct this in the next minor release - currently planned for the end of this week.

Best regards,
Ian (Passmark)

[MADStar]

I am currently working on a plugin for BIT using the demo version to evaluate BurninTest possibilities...

I noticed that Event Log notifications DO NOT reflect the Event type I am posting. I Post WARNINGS, they are displayed as INFORMATION then INFORMATION are WARNINGS etc...

Example in the plugin demo line 144 just after the WRITE bNewStatus
I insert a block to generate a WARNING in the log.

WARNING line should be labelled WARNING but they are not (see log below)

//////////////////////////////////////////
//Write
//////////////////////////////////////////
BitInterface->OUT_iStatus = PLUGIN_WRITING;
strn_clean_cpy(BitInterface->OUT_szStatus, PLUGIN_WRITE, PLUGIN_MAXDISPLAYTEXT);
BitInterface->OUT_bNewStatus = true; //flag that a new status string is available

// +MAD20060621 ------------------------------------------->
bErrorCondition = true; //just for demonstration

if (bErrorCondition)
{
//clear the last error, before passing a new one
while (BitInterface->IN_TestRunning &&
BitInterface->OUT_bNewError)
Sleep (500);
Sleep(500);
// BitInterface->OUT_iErrorCount++;
BitInterface->OUT_iErrorSeverity = ERRORWARNING;
strn_clean_cpy(BitInterface->OUT_szError,
" This should be a Warning!",
PLUGIN_MAXERRORTEXT);
BitInterface->OUT_bNewError = true;

}
// +MAD20060621 <----------------------------------------------------

// .... insert any write operations here
// eg. loop writing to disk
for (i=0;i<iNumWrites;i++)

......................................
Log produced by this code
------------------------------
******************
DETAILED EVENT LOG
******************
LOG NOTE: 2006-06-21 13:32:30, Status, PassMark BurnInTest V5.1 Pro 1005
LOG NOTE: 2006-06-21 13:32:30, Status, Main Tests started
CRITICAL : 2006-06-21 13:32:34, Plug-in, This should be a Warning!
WARNING : 2006-06-21 13:32:36, Plug-in, Plugin specified error message. This may be up to 100 characters long ABCDEFGHIJKLMNOPQRSTUVWXYZ
INFORMATION: 2006-06-21 13:32:37, Plug-in, This should be a Warning!
WARNING : 2006-06-21 13:32:39, Plug-in, Plugin specified error message. This may be up to 100 characters long ABCDEFGHIJKLMNOPQRSTUVWXYZ
INFORMATION: 2006-06-21 13:32:41, Plug-in, This should be a Warning!
WARNING : 2006-06-21 13:32:43, Plug-in, Plugin specified error message. This may be up to 100 characters long ABCDEFGHIJKLMNOPQRSTUVWXYZ
INFORMATION: 2006-06-21 13:32:44, Plug-in, This should be a Warning!
WARNING : 2006-06-21 13:32:46, Plug-in, Plugin specified error message. This may be up to 100 characters long ABCDEFGHIJKLMNOPQRSTUVWXYZ
INFORMATION: 2006-06-21 13:32:48, Plug-in, This should be a Warning!
WARNING : 2006-06-21 13:32:50, Plug-in, Plugin specified error message. This may be up to 100 characters long ABCDEFGHIJKLMNOPQRSTUVWXYZ
INFORMATION: 2006-06-21 13:32:51, Plug-in, This should be a Warning!
WARNING : 2006-06-21 13:32:53, Plug-in, Plugin specified error message. This may be up to 100 characters long ABCDEFGHIJKLMNOPQRSTUVWXYZ
LOG NOTE: 2006-06-21 13:32:55, Status, Test run stopped