A previous issue and PR were made (here #267 and here #268) to log per resource, the number of jobs for each status. For example, for the simulation tool Xcelium, how jobs are scheduled, queued, running, etc.
In the following #268 (comment), @AlexJones0 suggested this logic could be moved into a ResourceInstrumentation class. This would have some advantages, such as making it easy to pull the data and produce other reports at the end of runs. I looked into this while addressing the comments in the linked PR, but found it wasn't overly straightforward. I deferred it for now, but in the long run it would be a good change to make.
A previous issue and PR were made (here #267 and here #268) to log per resource, the number of jobs for each status. For example, for the simulation tool Xcelium, how jobs are scheduled, queued, running, etc.
In the following #268 (comment), @AlexJones0 suggested this logic could be moved into a
ResourceInstrumentationclass. This would have some advantages, such as making it easy to pull the data and produce other reports at the end of runs. I looked into this while addressing the comments in the linked PR, but found it wasn't overly straightforward. I deferred it for now, but in the long run it would be a good change to make.