Per a few recent discussions, log parsing could be greatly simplified and made more resilient if we weren't parsing live_backing logs for PERFHERDER_DATA log lines and failure lines for every task. A few steps to take: 1) Switch to consuming Perfherder artifacts (json would be ideal) 2) Switch to only consuming error_summary.json files (standardized naming would be great, per bug 1629716)*. This will also help with data Push Health provides since it relies on data from these logs. * In order to implement #2, we'd need to investigate whether we can get non-browser crash data some other way than from the live_backing log.
Bug 1646502 Comment 0 Edit History
Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.
Per a few recent discussions, log parsing could be greatly simplified and made more resilient if we weren't parsing live_backing logs for PERFHERDER_DATA log lines and failure lines for every task. A few steps to take: 1) Switch to consuming Perfherder artifacts (json would be ideal) 2) Switch to only consuming error_summary.json files (standardized naming would be great, per bug 1629716)*. This will also help with data Push Health provides since it relies on data from these logs. Currently we're doing both (if an error_summary file exists) with the TextLogError/Step lines used for the log viewer and the bug suggestions API. * In order to implement #2, we'd need to investigate whether we can get non-browser crash data some other way than from the live_backing log.