New issue
Advanced search Search tips

Issue 689628 link

Starred by 0 users
Status: Available
Owner: ----
Cc:
rockot@google.com
oksamyt@chromium.org
jamescook@chromium.org
sky@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 3
Type: Bug



Sign in to add a comment

Add crash detection to the service manager

Project Member Reported by e...@chromium.org, Feb 7 2017 
At least in unit tests (and probably elsewhere), we'll want to detect crashes of connected services (so we can fail the test).

Comment 1 by sky@chromium.org, Feb 7 2017

Cc: jamescook@chromium.org
This is likely related to 678683, which I believe James has started.

Comment 2 by jamescook@chromium.org, Feb 7 2017 

Yes, please see code in mash_runner.cc that registers quit closures for services. Probably the unit test runner will need to do something similar.

Comment 3 by roc...@chromium.org, May 29 2017

Cc: roc...@chromium.org
Components: Internals>ServiceManager
Owner: ----
Status: Available (was: Assigned)

Comment 4 by laforge@google.com, Nov 1 2017

Components: -Internals>ServiceManager Internals>Services>ServiceManager

Comment 5 by e...@chromium.org, Mar 9 2018

Cc: -e...@chromium.org
Un-cc-ing me from all bugs on my final day.

Comment 6 by roc...@chromium.org, Oct 15

Cc: oksamyt@chromium.org
Labels: -Proj-Mustash-Testing ServiceManagerImprovification
It doesn't seem like this is still important for Mus+ash specifically, but we will want to make sure we've considered crash detection and reporting before moving SM out of process on Chrome OS.

Comment 7 by roc...@chromium.org, Oct 17

Cc: -roc...@chromium.org rockot@google.com
►

Sign in to add a comment