a) Improve the submission job tracker, if we do not store the job-submission time, we will be replacing the value with the newly finished job from the multi-set/config queue.
So we can start saving the submission time to info.json
For backward compatibility, if the information is not there, "date" information is used as "submit_time".
b) Improve the running job counter, this relies on the rd_tool patchset(backend) https://github.com/xiph/rd_tool/pull/147, where for a given job we introduce a multi-job tracker.
Two main things
a) Improve the submission job tracker, if we do not store the job-submission time, we will be replacing the value with the newly finished job from the multi-set/config queue. So we can start saving the submission time to info.json For backward compatibility, if the information is not there, "date" information is used as "submit_time".
b) Improve the running job counter, this relies on the rd_tool patchset(backend) https://github.com/xiph/rd_tool/pull/147, where for a given job we introduce a multi-job tracker.