search

tud-zih-energy / FIRESTARTER

FIRESTARTER: A Processor Stress Test Utility. This repository contains the source code generator. Our releases (including the generated source code and precompiled binaries) are available at https://tu-dresden.de/zih/firestarter/.
GNU General Public License v3.0
116 stars 25 forks source link

2 question about error handle #33

Closed starcorn2020 closed 2 years ago

starcorn2020 commented 3 years ago

Hi guys,

I'm in charge of Firestarter test automation, It's few question about error handle.

command: Linux : ./FIRESTARTER -r --measurement --start-delta=2000 -t 86410 Windows : FIRESTARTER-windwos.exe -r -t 86410

  1. Have any key message for error handle? I try to reproduce the error, like press Ctrl+C or kill this program. but no additional message can be judged by program except running time.

  2. Have any additional message appeared when hardware can't keep stress test I try to reproduce this error, but machine offline without any word. Only thing can be judged by program is failed to ping remote OS.

BR, startcorn2020

bmario commented 3 years ago

I do not entirely understand your first question. But if you want more output from the program run, try the command line argument --report or --debug.

Regarding the second question, I understand that your machine is crashing. Please note the disclaimer:

WARNING: This software REALLY comes WITHOUT ANY WARRANTY! Some systems cannot handle the high load and crash due to overheating. It cannot be ruled out that the stress test damages the hardware! USE AT YOUR OWN RISK!

This warning is no joke; FIRESTARTER tries to maximize power consumption. If your machine crashes, it may be over-heated, or the power draw overwhelms the power supply. Regardless of the cause, this may damage your machine or worse. As it sounds like the system completely crashes, there is no message FIRESTARTER could produce. To sort that out, you'd need additional hardware monitoring via another software or even an external measurement device.

starcorn2020 commented 3 years ago

My question in 1. is that FIRESTARTER crashed/killed by self or anything accident appeared in process. Have anything additional key message or other messages printed in terminal, apart from using command line --report or --debug

I worked in server industry, it's necessary to pass stress test before release new server. Thank you for your reminder.

rschoene commented 3 years ago

If FIRESTARTER lead to a system shut-down, you should have a look into the system logs (e.g., via dmesg) to learn more about it.