New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.

Issue 630991 link

Starred by 2 users

Issue metadata

Status: Fixed
Owner:
Closed: Jul 2016
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Android
Pri: 2
Type: Bug



Sign in to add a comment

Chrome TOS dialog on Android breaks telemetry benchmarks

Project Member Reported by u...@chromium.org, Jul 25 2016

Issue description

Steps to reproduce:

1. Build chrome_public_apk  (I tested with at r407434).

2. Run benchmark:
./tools/perf/run_benchmark v8.browsing_mobile --browser=android-chromium --story-filter=facebook


Expected: the benchmark runs successfully

Actual: Chrome shows a popup window "By continuing, you agree to Chrome's Terms of Service and Privacy Notice" and the benchmark fails with
"EvaluateException: TypeError: Cannot read property 'pageScaleFactor' of undefined"

Note that telemetry passes --no-first-run command line flag t chrome. So it look like the the TOS dialog does not respect that flag.


CL that introduced TOS dialog: https://codereview.chromium.org/2062083002


gogerald@, ewald@, is there command line switch to disable TOS dialog?



 
Hmhh, I wonder how is the Android bots are still running telemetry test just fine on the waterfall. 

Comment 2 by u...@chromium.org, Jul 25 2016

Looks like the TOS popup depends on local state.

I tried two Nexus 4 devices. One of them shows the popup on every run. The other never shows the popup.
Lightweight FRE (TOS) is for view intents, there may have no tests use view intent and expect FRE disabled. Fix in this CL https://codereview.chromium.org/2177943002/. Verified with --disable-fre 

Comment 4 by u...@chromium.org, Jul 26 2016

Thanks for the fix!
I patched in the CL mentioned and set the appropriate flag but the pop up still shows up.

Command line:
tools/perf/run_benchmark v8.browsing_mobile --browser=exact --browser-executable=out/Release-android/apks/ChromePublic.apk --extra-browser-args="--disable-fre"


That's weird, I've verified. Could you check whether this switch has been passed to Chrome, https://cs.chromium.org/chromium/src/chrome/android/java/src/org/chromium/chrome/browser/ChromeSwitches.java?rcl=0&l=32
To be honest, I factory reset the device because I needed to take some measurements. I cannot reproduce it anymore.

Comment 8 by gogerald@google.com, Jul 28 2016

OK, '--disable-fre' should be able to disable both full and scoped FRE with that patch, will submit it, let me know if you can reproduce it again. 
Status: Fixed (was: Assigned)

Sign in to add a comment