Hi,
Is there an existing mechanism for tracking the overall resources used by a given tast test across CQ runs?
For example, if I want to understand how many minutes per week are spent running the
SELinuxProcesses tast test across all CQ runs. This would be helpful to understand, because it would help to determine how much benefit we could get by improving the test (or any other example test).
I see there's
go/crosbolt, but that seems to be more for tracking averages of specific metrics across releases, rather than getting a sense of CQ resources used over a given time.
Is there an existing mechanism that could be used to get at least an estimate for this?
Thanks!