Run Cronet perf test on Cronet bot

Run Cronet perf test on Cronet bot

Modify the bot recipe to:
1) Build quic_server and quic_client targeting the bot's native architecture
2) Build cronet_perf_test_apk targeting the device
3) Run the script to launch the benchmark

[pauljensen, 2015-08-17 14:17:39]

pauljensen@chromium.org changed reviewers:
+ xunjieli@chromium.org

[pauljensen, 2015-08-17 14:21:18]

Helen, PTAL.  This CL feels somewhat hacky so let me know if there's a
better/cleaner way I could be implementing this stuff.

[xunjieli, 2015-08-17 14:58:05]

I think this looks right as long as it works :). Should we also upload perf
stats to perf dashboard in this CL or in a follow up CL?

https://codereview.chromium.org/1292783004/diff/1/scripts/slave/recipes/crone...
File scripts/slave/recipes/cronet.py (right):

https://codereview.chromium.org/1292783004/diff/1/scripts/slave/recipes/crone...
scripts/slave/recipes/cronet.py:145: if 'run_perf_tests' in builder_config and
builder_config['run_perf_tests']:
Why do we run perf tests only on "Android Cronet Builder"? Should the other bots
with "run_tests = True" also run perf tests?

https://codereview.chromium.org/1292783004/diff/1/scripts/slave/recipes/crone...
scripts/slave/recipes/cronet.py:156: api.chromium.runhooks()
Suggest adding a name argument here, so it's clearer what this is for.
e.g. 
api.chromium.runhooks(name='runhooks for compiling quic server and client')

[xunjieli, 2015-08-17 22:15:11]

I got the reverse tethering working by commenting out 
    if (!session_->params().enable_insecure_quic &&
        !original_url.SchemeIs("https")) {
      continue;
    }
in
https://code.google.com/p/chromium/codesearch#chromium/src/net/http/http_stre....

So I guess the net::ERR_CONNECTION_REFUSED is because Cronet no longer has
insecure quic enabled.

When I ran the perf test, I also get a bunch of net::ERR_CONNECTION_REFUSED, so
the perf test is probably also affected by the fact that insecure quic is
disabled.
Should we fix this issue before landing this change on the bots?

[xunjieli, 2015-12-14 22:09:24]

On 2015/08/17 22:15:11, xunjieli wrote:
> I got the reverse tethering working by commenting out 
>     if (!session_->params().enable_insecure_quic &&
>         !original_url.SchemeIs("https")) {
>       continue;
>     }
> in
>
https://code.google.com/p/chromium/codesearch#chromium/src/net/http/http_stre....
> 
> So I guess the net::ERR_CONNECTION_REFUSED is because Cronet no longer has
> insecure quic enabled.
> 
> When I ran the perf test, I also get a bunch of net::ERR_CONNECTION_REFUSED,
so
> the perf test is probably also affected by the fact that insecure quic is
> disabled.
> Should we fix this issue before landing this change on the bots?

Looks like there's also some changes in telemetry. Even with QUIC stuff
commented out, the run.py script no longer works due to an error report in
tools/telemetry/telemetry/internal/util/ps_util.py. Paul, did you look at it?
What's the status on this? I was thinking maybe I could use your perf app and do
a quick measurement using memory_inspector.

[pauljensen, 2015-12-17 18:42:31]

I got it running again, see https://codereview.chromium.org/1536433002/

[xunjieli, 2016-03-31 14:15:11]

On 2015/12/17 18:42:31, pauljensen wrote:
> I got it running again, see https://codereview.chromium.org/1536433002/

That CL is landed. Can we land this too? Might need a rebase.

[pauljensen, 2016-03-31 14:17:01]

On 2016/03/31 14:15:11, xunjieli wrote:
> On 2015/12/17 18:42:31, pauljensen wrote:
> > I got it running again, see https://codereview.chromium.org/1536433002/
> 
> That CL is landed. Can we land this too? Might need a rebase.

Ya, we should land this too.  I'll add it to my work queue.