Overclock.net banner
1 - 5 of 5 Posts

·
Registered
Joined
·
218 Posts
Discussion Starter · #1 ·
I've just released an automation script for collecting data off a TestMem5 run.

Link to description, example, usage, caveats and download is here

Example run and output files:
Product Rectangle Font Screenshot Line Font Parallel Pattern Screenshot Rectangle

GitHub said:
  1. Take screenshot of area containing all windows with specified titles. Like HWiNFO*Sensor Status* or ZenTimings* or TestMem5*
  2. Collect information from TestMem5 interface
    • Current cycle
    • Number of errors
    • Log entries appeared on current cycle
  3. Store that information in files or filenames
  4. Do that only between TM5 cycles.
Why or when to use it?
  1. If you crash during the test you'll at least get the state from the last cycle.
  2. If you need to know during which cycle do the errors or individual thread crashes occur, but can't sit through the whole process.
  3. If you need to know how long does each cycle take.
  4. If you want to take screenshots of multiple windows and crop them to the least enclosing rectangle automatically.
 

·
Not New to Overclock.net
Joined
·
5,373 Posts
I've just released an automation script for collecting data off a TestMem5 run.

Link to description, example, usage, caveats and download is here

Example run and output files:
View attachment 2518510 View attachment 2518511



Why or when to use it?
  1. If you crash during the test you'll at least get the state from the last cycle.
  2. If you need to know during which cycle do the errors or individual thread crashes occur, but can't sit through the whole process.
  3. If you need to know how long does each cycle take.
  4. If you want to take screenshots of multiple windows and crop them to the least enclosing rectangle automatically.
nice.
 
1 - 5 of 5 Posts
Top