mash: Crash reporter should treat chrome --mus as a "mash" crash |
|||||
Issue descriptionFor the initial mushrome release we're just going to turn on mus-ws and mus-gpu. Those processes get --mus instead of --mash. Tweak the system-level crash reporter to treat all these processes as "mash" crashes. I think it's OK to treat all these as the same "product" in the crash dashboard. If we need a separate product for --mus it's easy to add later.
,
Apr 17 2017
The following revision refers to this bug: https://chromium.googlesource.com/chromiumos/platform2/+/4cf1aea253f2cf34e5fceae89ea00dd59520542d commit 4cf1aea253f2cf34e5fceae89ea00dd59520542d Author: James Cook <jamescook@chromium.org> Date: Mon Apr 17 21:06:21 2017 crash: Treat chrome --mus crashes as mash crashes The initial release of mustash will use --mus for its processes. A later release will add --mash for the system UI process. Treat both chrome --mus and chrome --mus as "mash" crashes. BUG= chromium:709093 TEST=added unit test Change-Id: If6a95c87e847c93042f5d2ffd63def06de7b1795 Reviewed-on: https://chromium-review.googlesource.com/470366 Commit-Ready: James Cook <jamescook@chromium.org> Tested-by: James Cook <jamescook@chromium.org> Reviewed-by: Mike Frysinger <vapier@chromium.org> [modify] https://crrev.com/4cf1aea253f2cf34e5fceae89ea00dd59520542d/crash-reporter/user_collector_test.cc [modify] https://crrev.com/4cf1aea253f2cf34e5fceae89ea00dd59520542d/crash-reporter/user_collector.cc
,
Apr 17 2017
,
May 30 2017
,
Aug 1 2017
,
Jan 22 2018
|
|||||
►
Sign in to add a comment |
|||||
Comment 1 by jamescook@chromium.org
, Apr 6 2017