Revert 185189.

Revert 185189.

This caused the NativeMessageBasic to timeout on cros and precise bots.
Example output:

ExtensionApiTest.NativeMessageBasic: 
[27122:27146:0228/021309:2707841027:ERROR:nss_util.cc(492)] Error initializing NSS with a persistent database (sql:/etc/fake_root_ca/nssdb): NSS error code: -8174
Xlib:  extension "GLX" missing on display ":9.0".
[27122:27122:0228/021309:2707849603:ERROR:gl_surface_glx.cc(326)] glxQueryVersion failed
[27122:27122:0228/021309:2707849652:ERROR:gl_surface_linux.cc(58)] GLSurfaceGLX::InitializeOneOff failed.
[27122:27122:0228/021309:2707849685:ERROR:compositor.cc(140)] Could not load the GL bindings
Xlib:  extension "RANDR" missing on display ":9.0".
Xlib:  extension "GLX" missing on display ":9.0".
[27153:27153:0228/021310:ERROR:gl_surface_glx.cc(326)] glxQueryVersion failed
[27153:27153:0228/021310:ERROR:gl_surface_linux.cc(58)] GLSurfaceGLX::InitializeOneOff failed.
[27153:27153:0228/021310:ERROR:nss_util.cc(492)] Error initializing NSS with a persistent database (sql:/etc/fake_root_ca/nssdb): NSS error code: -8174
Xlib:  extension "GLX" missing on display ":9.0".
[27171:27171:0228/021310:ERROR:gl_surface_glx.cc(326)] glxQueryVersion failed
[27171:27171:0228/021310:ERROR:gl_surface_linux.cc(58)] GLSurfaceGLX::InitializeOneOff failed.
[27171:27171:0228/021310:ERROR:nss_util.cc(492)] Error initializing NSS with a persistent database (sql:/etc/fake_root_ca/nssdb): NSS error code: -8174
[27122:27155:0228/021310:2708725028:ERROR:native_process_launcher.cc(94)] Could not find native host: com.google.chrome.test.echo
[27122:27155:0228/021310:2708736310:ERROR:native_process_launcher.cc(94)] Could not find native host: com.google.chrome.test.echo
[27122:27155:0228/021310:2708739432:ERROR:native_process_launcher.cc(94)] Could not find native host: com.google.chrome.test.echo
Killed (timed out).


> Require manifests for native messaging hosts.
> 
> Previously native messaging hosts were discovered by looking in the user 
> data directory. That approach is hard to use and is not reliable. Now 
> chrome will look for a host manifest file in a system-specific directory 
> and load that file to find host binary.
> 
> BUG=142915
> TBR=thakis@chromium.org
> 
> Review URL: https://chromiumcodereview.appspot.com/12285015

TBR=sergeyu@chromium.org
Committed: https://src.chromium.org/viewvc/chrome?view=rev&revision=185207

[tommi (sloooow) - chröme, 2013-02-28 10:39:52]

Committed patchset #1 manually as r185207.

[Sergey Ulanov, 2013-03-01 00:12:55]

This is clearly not caused by my CL - instead it seems to be a bug in the tests
infrastructure. The error message "Could not find native host..." was removed in
my CL, so it looks like the problem is that the bot was running old test binary
with newer test files, I'm not sure how that could happen. Going to try
relanding it.

[tommi (sloooow) - chröme, 2013-03-01 07:52:59]

OK, thanks.  I didn't go in and debug the issue.  There was a correlation
between your cl and the failing test so I tried revert and the test started
passing.  Good luck with relanding and thanks for understanding.


On Fri, Mar 1, 2013 at 1:12 AM, <sergeyu@chromium.org> wrote:

> This is clearly not caused by my CL - instead it seems to be a bug in the
> tests
> infrastructure. The error message "Could not find native host..." was
> removed in
> my CL, so it looks like the problem is that the bot was running old test
> binary
> with newer test files, I'm not sure how that could happen. Going to try
> relanding it.
>
>
https://codereview.chromium.**org/12386018/<https://codereview.chromium.org/1...
>

[Sergey Ulanov, 2013-03-02 03:18:31]

On Thu, Feb 28, 2013 at 11:52 PM, Tommi <tommi@chromium.org> wrote:

> OK, thanks.  I didn't go in and debug the issue.  There was a correlation
> between your cl and the failing test so I tried revert and the test started
> passing.  Good luck with relanding and thanks for understanding.
>

I wasn't complaining. I would revert it in these circumstances too :-)



>
>
> On Fri, Mar 1, 2013 at 1:12 AM, <sergeyu@chromium.org> wrote:
>
>> This is clearly not caused by my CL - instead it seems to be a bug in the
>> tests
>> infrastructure. The error message "Could not find native host..." was
>> removed in
>> my CL, so it looks like the problem is that the bot was running old test
>> binary
>> with newer test files, I'm not sure how that could happen. Going to try
>> relanding it.
>>
>>
https://codereview.chromium.**org/12386018/<https://codereview.chromium.org/1...
>>
>
>