Apparently, BEE does not update the metadata upon polling the status of a task until the task state changes. This does not give the proper runtime information for a user query while the job is running.
This example is longer running than in the examples and using slurm commands not slurmrestd (doesn't have runtime)
beeflow query 522
Running
task_name task_state JobId Partition RunTime NodeList Command
----------- ------------ -------- ----------- --------- ---------- ---------------------------------------------------------------
clamr RUNNING 16953860 general 00:00:04 cn243 /...l/beeworkdir/workdir/clamr-09ae/clamr-09ae.sh
ffmpeg WAITING
$ squeue -u p...
JOBID PARTITION NAME USER ST TIME NODES NODELIST(REASON)
16953860 general clamr-09 p... R 1:28 1 cn243
$ beeflow query 522
Running
task_name task_state JobId Partition RunTime NodeList Command
----------- ------------ -------- ----------- --------- ---------- ---------------------------------------------------------------
clamr COMPLETING 16953860 general 00:01:47 cn243 /..../beeworkdir/workdir/clamr-09ae/clamr-09ae.sh
ffmpeg WAITING
$ squeue -u pagrubel
JOBID PARTITION NAME USER ST TIME NODES NODELIST(REASON)
16953860 general clamr-09 p... CG 1:47 1 cn243
Apparently, BEE does not update the metadata upon polling the status of a task until the task state changes. This does not give the proper runtime information for a user query while the job is running.
This example is longer running than in the examples and using slurm commands not slurmrestd (doesn't have runtime)