If a MLonMCU benchmarking session is interrupted right inside a benchmarking session, no report will be produced.
Ideally we should catch an CTRL-C signal to stop the running jobs manually and Update the report using the data which was already available an the previous stage. Finally append a new colum to the report which indicates which rows are incomplete due to beeing canceled by the user and make sure to return a non-zero exit code to the shell.
Optional: Check if CTRL+C is hit multiple times and exit directly (Maybe this works right out-of-the box?)
If a MLonMCU benchmarking session is interrupted right inside a benchmarking session, no report will be produced.
Ideally we should catch an CTRL-C signal to stop the running jobs manually and Update the report using the data which was already available an the previous stage. Finally append a new colum to the report which indicates which rows are incomplete due to beeing canceled by the user and make sure to return a non-zero exit code to the shell.
Optional: Check if CTRL+C is hit multiple times and exit directly (Maybe this works right out-of-the box?)