diff options
| author | erikwright@chromium.org <erikwright@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98> | 2010-09-28 13:46:10 +0000 |
|---|---|---|
| committer | erikwright@chromium.org <erikwright@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98> | 2010-09-28 13:46:10 +0000 |
| commit | 2014db003dcdc6e45aed7ba6d5e51819354ef66a (patch) | |
| tree | c5b8c662f9b755cb5565a375724ad2898313fd51 /chrome_frame/test/ui_test.cc | |
| parent | 1e0c66748a7f459f454c91a88602346c0f5207fa (diff) | |
| download | chromium_src-2014db003dcdc6e45aed7ba6d5e51819354ef66a.zip chromium_src-2014db003dcdc6e45aed7ba6d5e51819354ef66a.tar.gz chromium_src-2014db003dcdc6e45aed7ba6d5e51819354ef66a.tar.bz2 | |
Modify chrome_frame_test_utils to react gracefully if crash_service is already running before test launch (i.e., no spurious error message, leave it running as it was). Also, if it needs to be started, rather than waiting 500ms and assuming it is launched, poll the pipe and return when server is listening.
BUG=None
TEST="chrome_frame_tests" (optionally with a --gtest_filter=...). Allow it to run to completion (notice crash service starts and then stops). Launch test suite again, kill it after crash_service starts, launch it again. Notice it does not start new crash_service, nor log a needless "Failed to terminate process" warning. Watch debug.log for traces about the launch of crash_service.
Review URL: http://codereview.chromium.org/3437012
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@60778 0039d316-1c4b-4281-b951-d872f2087c98
Diffstat (limited to 'chrome_frame/test/ui_test.cc')
0 files changed, 0 insertions, 0 deletions