Add support for cc_perftests and other non-telemetry gtest based tests.

testing/scripts/common.py

Index: testing/scripts/common.py
diff --git a/testing/scripts/common.py b/testing/scripts/common.py
index f3617c7111ba0ada2a0bf3ce6e0c2de9e8051cf9..d7d29528334b5da96aa49884e1522fab5492e623 100644
--- a/testing/scripts/common.py
+++ b/testing/scripts/common.py
@@ -31,6 +31,7 @@ def run_script(argv, funcs):
   parser.add_argument('--build-config-fs')
   parser.add_argument('--paths', type=parse_json, default={})
   parser.add_argument('--properties', type=parse_json, default={})
+  parser.add_argument('--args', type=parse_json, default=[])

[iannucci, 2015/02/23 18:02:49]

why is the introduction of a new argument necessary? Why can't the relevant info
be shuttled through properties?

[iannucci, 2015/02/23 18:04:33]

Actually... it looks like this isn't even used by the new script? AFAICT
`args.properties` is actually referring to the --properties option above.

[shatch, 2015/02/23 20:14:21]

This was Pawel's preference when we spoke over email.
The new argument is used to get the script args.

[Paweł Hajdan Jr., 2015/02/23 20:46:30]

I consider properties to be the same for all script invocations, and describe
the environment of the build.

Args can be different per invocation, e.g. you could have the same script but
invoked in different steps with different args (e.g. a gtest step with different
test names like base_unittests, net_unittests, etc).

I think the distinction is important and actually results in cleaner code.

 
   subparsers = parser.add_subparsers()