Fix name/path separator for telemetry_unittests test names.

Fix name/path separator for telemetry_unittests test names.

Previously we were using the hard-coded '/' separator for
components of a test name (which was what the layout tests use),
but telemetry uses '.' instead.

R=ojan@chromium.org
BUG=399371, 425694
Committed: http://src.chromium.org/viewvc/chrome?view=rev&revision=292664

[Dirk Pranke, 2014-10-24 00:06:22]

Patchset #1 (id:1) has been deleted

[Dirk Pranke, 2014-10-24 00:12:45]

Patchset #1 (id:20001) has been deleted

[Dirk Pranke, 2014-10-24 00:12:51]

Patchset #1 (id:40001) has been deleted

[Dirk Pranke, 2014-10-24 00:15:23]

Ojan, please take a look?

Note that the test format does currently contain a 'path_separator' field, and
the non-layout-test python-based tests all pass '.' . 

You had modified the spec to claim that this was aspirational, but it does
actually exist today.

(run-webkit-tests doesn't pass the field, and the flakiness dashboard doesn't
handle '.', but we probably need to fix those things. I changed the spec to note
that we should make this required).

https://codereview.chromium.org/674023002/diff/60001/scripts/slave/recipe_mod...
File scripts/slave/recipe_modules/json/api.py (left):

https://codereview.chromium.org/674023002/diff/60001/scripts/slave/recipe_mod...
scripts/slave/recipe_modules/json/api.py:85: # TODO(phajdan.jr): Rename to
LayoutTestResultsOutputPlaceholder.
I removed this and the other TODOs since this class is being used by the other
PythonBased tests now. We can certainly rename it to something if need be to
disambiguate it from the gtest-based stuff, but LayoutTestResults would be the
wrong thing to rename it to.

[szager1, 2014-10-24 20:26:05]

szager@chromium.org changed reviewers:
+ szager@chromium.org

[szager1, 2014-10-24 20:26:06]

It looks good to me, but the changes to the test expectations look weird.  Can
you verify they make sense?

[Dirk Pranke, 2014-10-24 20:43:20]

On 2014/10/24 20:26:06, szager1 wrote:
> It looks good to me, but the changes to the test expectations look weird.  Can
> you verify they make sense?

I think that's just git getting confused with the new file. I'll re-upload w/
--no-find-copies .

[Dirk Pranke, 2014-10-24 20:44:50]

fixed ...

[szager1, 2014-10-24 20:54:47]

lgtm

[Dirk Pranke, 2014-10-24 20:57:58]

The CQ bit was checked by dpranke@chromium.org

[commit-bot: I haz the power, 2014-10-24 20:58:29]

CQ is trying da patch. Follow status at
 https://chromium-cq-status.appspot.com/patch-status/674023002/80001

[commit-bot: I haz the power, 2014-10-24 21:00:10]

Committed patchset #2 (id:80001) as 292664