Re-enable ServiceManagerContextTest.TerminateOnServiceQuit
This was disabled on Chrome OS + ASAN due to flakiness. I suspect the flakiness is caused by use of fork() in a multithreaded environment, via base::GetAppOutputAndError. This CL changes the offending test to not use the ContentBrowserTest fixture and instead simply call base::GetAppOutputAndError from a single-threaded unit test. The manually launched browser test in the launched subprocess remains unchanged. Renames the browser test fixture to ServiceManagerContentBrowserTest to disambiguate from the new non-browser-test test case. Bug: 803188 Change-Id: I5d1be42cb35ccc6ec79ed1cbda83018291aecaa2 TBR=jam Change-Id: I5d1be42cb35ccc6ec79ed1cbda83018291aecaa2 Reviewed-on: https://chromium-review.googlesource.com/875269 Commit-Queue: Ken Rockot <rockot@chromium.org> Reviewed-by:James Cook <jamescook@chromium.org> Cr-Commit-Position: refs/heads/master@{#530377}
Showing
Please register or sign in to comment