[Telemetry] Move telemetry/examples to telemetry/experimental.

[Telemetry] Move telemetry/examples to telemetry/experimental.

This is so that we can use the telemetry/examples folder for putting an examples
end to end benchmark.

BUG=482227
Committed: https://crrev.com/88bb32230eda97260936c965b3eb189ce93e1c48
Cr-Commit-Position: refs/heads/master@{#330629}

[nednguyen, 2015-04-28 23:23:26]

nednguyen@google.com changed reviewers:
+ aiolos@chromium.org, dtu@chromium.org

[aiolos (Not reviewing), 2015-04-28 23:38:22]

On 2015/04/28 23:23:26, nednguyen wrote:

IMO, if these files aren't useful enough to be kept in the examples folder, we
should just delete them. I think it would make sense to keep the credentials
example. But the rest of them can either be trashed or should be updated and
included in the example for 482227.

[dtu, 2015-05-01 23:24:57]

On 2015/04/28 23:38:22, aiolos wrote:
> On 2015/04/28 23:23:26, nednguyen wrote:
> 
> IMO, if these files aren't useful enough to be kept in the examples folder, we
> should just delete them. I think it would make sense to keep the credentials
> example. But the rest of them can either be trashed or should be updated and
> included in the example for 482227.

+1, yes, most of these things are no longer going to be in the public API, so we
don't want people to use them as examples anyway.

[aiolos (Not reviewing), 2015-05-01 23:59:25]

aiolos@chromium.org changed reviewers:
+ erikchen@chromium.org

[aiolos (Not reviewing), 2015-05-02 00:01:16]

aiolos@chromium.org changed reviewers:
- erikchen@chromium.org

[nednguyen, 2015-05-19 15:35:00]

Removed not very useful files and keep the useful ones:
+measure_trace.py is the offline mode of TBM, feed it a trace and it will output
timeline based metrics values.
+telemetry_perf_test.py measures the roundtrip time of talking to android chrome
through usb.

[dtu, 2015-05-19 17:45:58]

https://codereview.chromium.org/1111103002/diff/20001/tools/telemetry/example...
File tools/telemetry/examples/credentials_example.json (left):

https://codereview.chromium.org/1111103002/diff/20001/tools/telemetry/example...
tools/telemetry/examples/credentials_example.json:1: {
We still need this for completeness for external contributors.

https://codereview.chromium.org/1111103002/diff/20001/tools/telemetry/experim...
File tools/telemetry/experimental/telemetry_perf_test.py (right):

https://codereview.chromium.org/1111103002/diff/20001/tools/telemetry/experim...
tools/telemetry/experimental/telemetry_perf_test.py:1: #!/usr/bin/env python
I think this stuff is no longer going to be in the public API. We don't support
using Telemetry for just browser automation.

[nednguyen, 2015-05-19 18:11:39]

https://codereview.chromium.org/1111103002/diff/20001/tools/telemetry/example...
File tools/telemetry/examples/credentials_example.json (left):

https://codereview.chromium.org/1111103002/diff/20001/tools/telemetry/example...
tools/telemetry/examples/credentials_example.json:1: {
On 2015/05/19 17:45:58, dtu wrote:
> We still need this for completeness for external contributors.

Done.

https://codereview.chromium.org/1111103002/diff/20001/tools/telemetry/experim...
File tools/telemetry/experimental/telemetry_perf_test.py (right):

https://codereview.chromium.org/1111103002/diff/20001/tools/telemetry/experim...
tools/telemetry/experimental/telemetry_perf_test.py:1: #!/usr/bin/env python
On 2015/05/19 17:45:58, dtu wrote:
> I think this stuff is no longer going to be in the public API. We don't
support
> using Telemetry for just browser automation.

This is useful for benchmarking the latency between telemetry & browser. That's
why I put this in experimental/ rather than examples/ or any public facing part.

Also we should talk about using telemetry as a library vs telemetry as a
framework.

[nednguyen, 2015-05-19 18:13:12]

Patchset #3 (id:40001) has been deleted

[nednguyen, 2015-05-19 18:15:25]

Patchset #4 (id:80001) has been deleted

[dtu, 2015-05-19 19:53:56]

On 2015/05/19 18:11:39, nednguyen wrote:
>
https://codereview.chromium.org/1111103002/diff/20001/tools/telemetry/example...
> File tools/telemetry/examples/credentials_example.json (left):
> 
>
https://codereview.chromium.org/1111103002/diff/20001/tools/telemetry/example...
> tools/telemetry/examples/credentials_example.json:1: {
> On 2015/05/19 17:45:58, dtu wrote:
> > We still need this for completeness for external contributors.
> 
> Done.
> 
>
https://codereview.chromium.org/1111103002/diff/20001/tools/telemetry/experim...
> File tools/telemetry/experimental/telemetry_perf_test.py (right):
> 
>
https://codereview.chromium.org/1111103002/diff/20001/tools/telemetry/experim...
> tools/telemetry/experimental/telemetry_perf_test.py:1: #!/usr/bin/env python
> On 2015/05/19 17:45:58, dtu wrote:
> > I think this stuff is no longer going to be in the public API. We don't
> support
> > using Telemetry for just browser automation.
> 
> This is useful for benchmarking the latency between telemetry & browser.
That's
> why I put this in experimental/ rather than examples/ or any public facing
part.
> 
> Also we should talk about using telemetry as a library vs telemetry as a
> framework.

Yeah. There are definitely still times when people have just wanted browser
automation without perf testing.

lgtm

[nednguyen, 2015-05-19 19:54:41]

The CQ bit was checked by nednguyen@google.com

[commit-bot: I haz the power, 2015-05-19 19:55:44]

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

[commit-bot: I haz the power, 2015-05-19 22:10:52]

Committed patchset #3 (id:60001)

[commit-bot: I haz the power, 2015-05-19 22:12:04]

Patchset 3 (id:??) landed as
https://crrev.com/88bb32230eda97260936c965b3eb189ce93e1c48
Cr-Commit-Position: refs/heads/master@{#330629}