headless: Don't run tests during the build

testing/buildbot/chromium.fyi.json

Index: testing/buildbot/chromium.fyi.json
diff --git a/testing/buildbot/chromium.fyi.json b/testing/buildbot/chromium.fyi.json
index 1d1b7a7a13c75a7af073cd424aaf1d01adab6393..01c22a32422d76e76a8e67cb770519d631009ab1 100644
--- a/testing/buildbot/chromium.fyi.json
+++ b/testing/buildbot/chromium.fyi.json
@@ -9711,6 +9711,12 @@
         },
         "test": "headless_unittests"
       }
+    ],
+    "scripts": [
+      {
+        "name": "client_api_generator_unittest",
+        "script": "headless/lib/browser/client_api_generator_unittest.py"

[perezju, 2016/10/11 10:25:01]

It looks like other scripts are given relative to src/testing/scripts/, and many
are just wrappers around the actual test scripts, see:

https://chromium.googlesource.com/chromium/src/+/master/testing/scripts

+phajdan who should know more about these.

[Paweł Hajdan Jr., 2016/10/11 18:10:01]

Yup. Not only they need to be there, but also there's specific protocol for
this. See existing examples and let me know if you have any questions.

My general design suggestion would be to write generic python unit test script,
which takes specific file or directory as argument.

Dirk may have further suggestions, e.g. related to his typ test harness.

[Dirk Pranke, 2016/10/11 18:23:28]

You should look at the scripts in //testing/scripts (like telemetry_unittests.py
or webkit_unittests.py), and, yes, using //third_party/typ will probably
simplify this. 

We don't currently have a single wrapper script. It's possible that we could
write one; I'm not sure if the script would end up growing too many arguments to
be worth it, though.

+      }
     ]
   },
   "LTO Linux": {