Remove GN test from bots.

Remove GN test from bots.

This is causing mysterious output failures on the bots

TBR=phajdan.jr

Committed: https://src.chromium.org/viewvc/chrome?view=rev&revision=285388

[brettw, 2014-07-24 22:08:35]

The failures look like this:
http://build.chromium.org/p/tryserver.chromium/builders/linux_chromium_rel/bu...

Do you know what could be causing this? gn_unittests is not using the new test
launcher (calls gtest directly). Is the infrastructure expecting some different
style of output?

[brettw, 2014-07-24 22:16:25]

Committed patchset #1 manually as r285388 (presubmit successful).

[Paweł Hajdan Jr., 2014-07-28 14:40:28]

LGTM

I think https://codereview.chromium.org/318543002 is what broke it. Please let
me know if you have more questions.

[brettw, 2014-07-28 17:05:23]

So is there no way to run a single-process test on the bots? This test is slower
to run multiprocess and the test output is ugly, so I much prefer single
process.

[Paweł Hajdan Jr., 2014-08-11 11:17:08]

On 2014/07/28 17:05:23, brettw wrote:
> So is there no way to run a single-process test on the bots? This test is
slower
> to run multiprocess and the test output is ugly, so I much prefer single
> process.

We can discuss the specific issues - I'm really not sure how to respond to it.

There were several threads about the new test launcher on chromium-dev (since
late 2013) and I don't remember a single complaint about the output being
"ugly".

I'm still open to further improvements to the test launcher. It seems to me
"ugly" output isn't necessarily enough reason not to run the test at all,
especially that *all* other gtest-based tests use it and the changes were
announced and discussed before they were deployed.