run_benchmark --browser=exact is not working on Android |
||||||
Issue descriptionThe command below is not working for me: $ tools/perf/run_benchmark run system_health.memory_mobile --browser=exact --browser-executable=out/AndroidRelease/apks/ChromePublic.apk --story-filter=load:search:google perezju@ can you take a look? Thanks!
,
Sep 15 2017
,
Sep 15 2017
Try using --device=android. $ tools/perf/run_benchmark run system_health.memory_mobile --browser=exact --device=android --browser-executable=out/Release/apks/ChromePublic.apk --story-filter=load:search:google works for me.
,
Sep 19 2017
Ned, the way telemetry picks up and selects a browser is a bit of a mess. We might need to spend a bit of time thinking how to streamline/simplify things? Interestingly, some of the internal bots seem to be fine and happy running: tools/perf/run_benchmark -v --upload-results --browser=exact --browser-executable out/Release/apks/Monochrome.apk --output-format=chartjson --also-run-disabled-tests memory.dual_browser_test
,
Sep 19 2017
Yes. The whole device & browser discovery logic is a mess. I have this doc a while ago: https://docs.google.com/document/d/14GYqOmG2A8L1-biEDFSvgY9bFWWm7ruaCzgHd8Vmx00/edit#heading=h.aw6rglmwb8kv (Googler only, Some idea may still apply and some may not)
,
Sep 19 2017
Yeah, I remember that doc. I'll keep this in my plate with a low Pri, and maybe work on it when I find some spare cycles.
,
Apr 30 2018
Let's close this in favor of issue 799950 where we had the latest discussions around this issue.
,
Jan 16
,
Jan 16
|
||||||
►
Sign in to add a comment |
||||||
Comment 1 by perezju@chromium.org
, Sep 13 2017