Fix and enable mojo:media_pipeline_integration_apptests.

mojo/tools/data/apptests

Index: mojo/tools/data/apptests
diff --git a/mojo/tools/data/apptests b/mojo/tools/data/apptests
index 3987e89314b9388595915e0d37fae1361080573c..ecd645a813f1bb79c189a177b632ccad1ce9a247 100644
--- a/mojo/tools/data/apptests
+++ b/mojo/tools/data/apptests
@@ -83,12 +83,14 @@ if config.target_os != config.OS_ANDROID:
 #      'args': ['--use-x11-test-config',
 #               '--override-use-gl-with-osmesa-for-tests']
 #    },
-    # TODO(xhwang): Fix and enable mojo:media_pipeline_integration_apptests.
-    # http://crbug.com/501417
     {
       'test': 'mojo:media_apptests',
       'type': 'gtest_isolated',
     },
+    {
+      'test': 'mojo:media_pipeline_integration_apptests',

[sky, 2016/01/21 20:31:39]

Is this depended on by the target the builders look for to determine if
mojo_apptests should run?

[jrummell, 2016/01/26 19:47:41]

I think so, assuming media_apptests was done properly. The dependency has
previously been checked into media/mojo/services/BUILD.gn (in group("tests"),
the first file in this CL, lines 258-270).

I also checked, and the tests did run on the trybots (for
linux_chromium_rel_ng).

[sky, 2016/01/26 23:27:23]

I think it safer to update the mojo_apptests in src/BUILD.gn (I recently added
it, there is a comment in this file to that effect if you sync to tip of tree).

[jrummell, 2016/01/27 00:55:27]

Done.

+      'type': 'gtest_isolated',
+    },
     # TODO(crbug.com/560626): Fix and enable mus_apptests on Android.
     mus_apptests,
     {