This is a dup of  http://crbug.com/803188  and presumably introduced when the test was reenabled in https://chromium-review.googlesource.com/875269

I take the above back: the patch reenabled it on Chrome OS + ASAN, so it shouldn't affect Linux.

The last three builds are green  but the flakiness dashboard does suggest the test is flaky on Linux ASan LSan.

Reassigning to rockot@ as owner to follow up. Meanwhile, depending on how flaky this is, I'll proceed with disabling the test.

This just looks like a legitimate timeout rather than anything misbehaving. While this is surprising given that the test doesn't run for very long, I'll re-disable it on ASAN for now.

The following revision refers to this bug:
  https://chromium.googlesource.com/chromium/src.git/+/27511833af48cf5702376a1f3296d7d35f3d2857

commit 27511833af48cf5702376a1f3296d7d35f3d2857
Author: Ken Rockot <rockot@chromium.org>
Date: Fri Jan 19 21:18:00 2018

Disable ServiceManagerContextTest.TerminateOnServiceQuit for ASAN

This flakily times-out on ASAN bots.

Bug: 803814
Change-Id: I2639e4b36c6dff9021744bc753805b085e161a4a

TBR=jamescook

Change-Id: I2639e4b36c6dff9021744bc753805b085e161a4a
Reviewed-on: https://chromium-review.googlesource.com/876727
Reviewed-by: Ken Rockot <rockot@chromium.org>
Commit-Queue: Ken Rockot <rockot@chromium.org>
Cr-Commit-Position: refs/heads/master@{#530613}
[modify] https://crrev.com/27511833af48cf5702376a1f3296d7d35f3d2857/content/browser/service_manager/service_manager_context_browsertest.cc