Issue metadata
Sign in to add a comment
|
Async tests in headless_browsertests became flaky |
||||||||||||||||||
Issue descriptionTargetDomainCreateAndDeleteBrowserContextTest.RunAsyncTest: https://ci.chromium.org/buildbot/chromium.fyi/Headless%20Linux%20%28dbg%29/39782 https://ci.chromium.org/buildbot/chromium.fyi/Headless%20Linux%20%28dbg%29/39737 TargetDomainDisposeContextFailsIfInUse.RunAsyncTest: https://ci.chromium.org/buildbot/chromium.fyi/Headless%20Linux%20%28dbg%29/39746 https://ci.chromium.org/buildbot/chromium.fyi/Headless%20Linux%20%28dbg%29/39771 Errors appear to have this form: [29489:29510:0105/133812.825564:549778151:FATAL:service_manager.cc(154)] Check failed: false. The Service Manager prevented service "content_browser" from binding interface "content::mojom::Child" in target service "content_renderer". You probably need to update one or more service manifests to ensure that "content_renderer" exposes "content::mojom::Child" through a capability and that "content_browser" requires that capability from the "content_renderer" service. +sky The service manifests appear to be set up correctly: https://cs.chromium.org/chromium/src/content/public/app/mojo/content_browser_manifest.json?sq=package:chromium&dr=C https://cs.chromium.org/chromium/src/content/public/app/mojo/content_renderer_manifest.json?sq=package:chromium&dr=C Do you know why the tests could have started failing?
,
Jan 6 2018
Correct. It used to just be ignorable log spam and now it's a DCHECK. This particular DCHECK surprises me though. I'll take a look.
,
Jan 6 2018
> Are you sure the warning is new? I only see it in the most recent runs of Headless Linux dbg https://ci.chromium.org/buildbot/chromium.fyi/Headless%20Linux%20%28dbg%29/?limit=200
,
Jan 6 2018
,
Oct 17
|
|||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||
Comment 1 by sky@chromium.org
, Jan 5 2018