crostini: Bucket RestarterResult metrics after an unclean start separately
After e.g. a Chrome crash we're in a known unsupported state, we tell the user this but allow them to continue. Restarter errors in this case should go in their own bucket, since we're in a different starting state with its own set of failure modes. Bug: 1142321 Test: Launch Crostini before/after a crash, check chrome://histograms Change-Id: I7927b18f6d98572b6a083426eb3d8a7a05f13f52 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2532135 Commit-Queue: David Munro <davidmunro@google.com> Reviewed-by:Nicholas Verne <nverne@chromium.org> Reviewed-by:
Michael Lippautz <mlippautz@chromium.org> Reviewed-by:
Mark Pearson <mpearson@chromium.org> Cr-Commit-Position: refs/heads/master@{#830067}
Showing
Please register or sign in to comment