I don't think the `INFO` vs `ERROR` thing is relevant. Looking at all the logs you linked, the proper error is showing up in the treeherder errorsummary. Fyi we use structured logs to propagate assertions/crashes up (for most suites). Those mozharness regexes are just fallbacks for suites that don't support structured logging. The issue is that this bug has a very generic title, so sheriffs are starring anything that crashes against it. I believe with force-crash the browser if we hit an assertion too, so that's why those are also appearing here. Basically anything with the string "A content process crashed and MOZ_CRASHREPORTER_SHUTDOWN is set, shutting down". So the solution is to file separate bugs for each underlying issue, and ask the sheriffs to star each issue against the appropriate bug (possibly even closing this to prevent further starring here).
Bug 1588877 Comment 28 Edit History
Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.
I don't think the `INFO` vs `ERROR` thing is relevant. Looking at all the logs you linked, the proper error is showing up in the treeherder errorsummary. Fyi we use structured logs to propagate assertions/crashes up (for most suites). Those mozharness regexes are just fallbacks for suites that don't support structured logging. The issue is that this bug has a very generic title, so sheriffs are starring anything that crashes against it. I believe we force-crash the browser if we hit an assertion too, so that's why those are also appearing here. Basically anything with the string "A content process crashed and MOZ_CRASHREPORTER_SHUTDOWN is set, shutting down". So the solution is to file separate bugs for each underlying issue, and ask the sheriffs to star each issue against the appropriate bug (possibly even closing this to prevent further starring here).