Open Bug 1821509 Opened 2 years ago Updated 1 year ago

consider mozharness creating errorsummary.json for INFRA/harness errors

Categories

(Firefox Build System :: Task Configuration, task, P3)

task

Tracking

(Not tracked)

People

(Reporter: jmaher, Unassigned)

References

(Blocks 1 open bug)

Details

we don't have errorsummary.json unless the in browser harness creates one, we should be able to handle this at the harness and mozharness level.

If no tests were run, then it is infrastructure and we can find a standardized message.

If some or all tests were run, then append to errorsummary.json with the INFRA message.

the benefit of doing this is we can start to shift away from raw log parsing in treeherder, tools like mozci/bugbug can have better meta data, dashboards about what ran and what failures we have seen will have more accurate parsable metadata.

Severity: -- → S4
Priority: -- → P3
You need to log in before you can comment on or make changes to this bug.