If this is your first visit, be sure to
check out the FAQ by clicking the
link above. You may have to register
before you can post: click the register link above to proceed. To start viewing messages,
select the forum that you want to visit from the selection below.
All of the main errors are listed in the file BITErrorClassification.txt in the BurnInTest directory. They are also shown with a description in the User guide (and help file) in section 12.3 "Common Test Error Messages": http://www.passmark.com/ftp/BIT_Users_Guide_Ed7_0.pdf
As these error messages are configurable, the strings could change.
Ah. I looked through the documentation, but I guess I missed that part. That should work perfectly.
All of the main errors are listed in the file BITErrorClassification.txt in the BurnInTest directory. They are also shown with a description in the User guide (and help file) in section 12.3 "Common Test Error Messages": http://www.passmark.com/ftp/BIT_Users_Guide_Ed7_0.pdf
As these error messages are configurable, the strings could change.
When the BIT finishes, I need to be able to determine if it passed or failed. If it fails, I need to know why.
But because of the way the test is formatted, it makes it difficult to find out the failures. I checked the log in normal text format and HTML and neither makes it very easy to determine the cause of failure.
At the moment, I parsing the file and checking for "TEST RUN FAILED." If it's found, I fail the test and if not, I pass it. But I need details.
So, is there a list of possible failures I could just look for? So the failure might say, "Memory test failure" or "error allocating ram", etc. If I had a list of possible errors, I could just look for those and that would work for me.
The only tests I'm running are CPU, ODD, RAM, 2D/3D, and disks.
Leave a comment: