You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The repository folder scripts/plotting contains all relevant files.
All plotting files (*.py) are copied from that repository folder during the workflow run to the plot/ folder in the S3 benchmark folder (e.g., 20200804_160933/plot).
The workflow run waits until all benchmark runs are completed and then starts the plotting generation.
Until now, the workflow did not know when the benchmark is finished. I added a loop until (VM state == running) { sleep 1 min } for blocking waiting.
As yesterday a workflow run aborted and the VM was running for 15 hrs, I added a timeout parameter that determines when the VM is automatically halted and also determines how long we will wait for the benchmark run to finish before we continue with the plot generation.
The halt command is sent to the VM as a background job that is invoked after the given timeout (i.e., 60 mins).
After all benchmark runs are completed, the plot generation job starts.
It generates the plots and saves them in S3 (all in Python code, see plot_all.py)
Originally posted by @pjattke in #1 (comment)
The text was updated successfully, but these errors were encountered: