Open YehorYudinIPP opened 9 months ago
It looks like this instance started its run but didn't shut down cleanly. When that happens, the shutdown isn't recorded in the database, and so MUSCLE3 doesn't know how long it ran and cannot calculate which percentage of the core's time it used.
There should be a test and a nice error message here at least, so thanks for reporting this!
Could you check the log and see if it says anything about the stop
instance crashing or shutting down because something else crashed?
Also, which version of MUSCLE3 are you using?
Thanks Lourens! I updated the comment, it's MUSCLE3 0.7.0
Indeed, the workflow failed due to an error in a turbulence_sim
component:
muscle_manager 2023-10-06 00:15:14,185 ERROR libmuscle.manager.instance_manag er: Instance turbulence_sim quit with error 38
Which in its turn failed due to overcrowding my cluster's hard drive, unfortunately:
forrtl: Disk quota exceeded forrtl: severe (38): error during write, unit 42, file /cobra/u/yyudin/code/MFW /muscle3/workflow/run_fusion_gem_multiimpl_20231005_criteria/instances/turbulen ce_sim/workdir/p02.dat
Okay, yes, then the issue here is that there should be a better error message. I'll go fix that. Note that 0.7.1 is out with several fixes to the profiling system (including that muscle3 profile -t
is now working), so you may want to upgrade :smile:
Calling
muscle3 profile -r performance.sqlite
fails withKeyError: 'stop'
, wherestop
is the name of a workflow instance. The version of MUSCLE3 library is 0.7.0The total error stack in Python is: