Treeherder already parses error summary files, and recently (Bug 1671422) a duration was added for each group_result. Here is an example:
https://firefoxci.taskcluster-artifacts.net/ZKB7LpfqTliUz3LzqpPvLg/0/public/test_info//mochitest-browser-chrome_errorsummary.log

Because of this, we would like to have this data stored in Treeherder alongside what test groups were scheduled for a given task.

I want to make sure this isn't duplicated with Bug 1669548 as that is for task level information to allow us to query only treeherder and not taskcluster.

:camd, if you could comment on this as to what effort this is (1 day, 1 week, single line change, etc.)- maybe we could include this in an upcoming treeherder sprint.

It looks like this is just adding duration for group_status. That being the case, we would add the duration field to this model:

https://github.com/mozilla/treeherder/blob/b78e3b839bdb53e9700c3ccc7ebe808f79338a97/treeherder/model/models.py#L1117-L1127

Then you would add the value to the model during ingestion here:

https://github.com/mozilla/treeherder/blob/4116ec796e17dd799a964a7cf1d1ccacb3f9a027/treeherder/log_parser/failureline.py#L116-L133

Then the hardest part (not that hard) would be in deciding how to get that to the user. You could create a new endpoint, or modify the return value of the existing endpoint which is generated here:

https://github.com/mozilla/treeherder/blob/4116ec796e17dd799a964a7cf1d1ccacb3f9a027/treeherder/log_parser/failureline.py#L178-L185
and
https://github.com/mozilla/treeherder/blob/b78e3b839bdb53e9700c3ccc7ebe808f79338a97/treeherder/webapp/api/push.py#L369-L384

I'm guessing this is 1-2 days work.

thanks :camd, this might be a good_second_bug for a sprint