New issue
Advanced search Search tips

Issue 798876 link

Starred by 0 users

Issue metadata

Status: Assigned
Owner:
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 3
Type: Bug



Sign in to add a comment

graphics_Idle should use normal/logged in browser

Project Member Reported by achuith@chromium.org, Jan 3 2018

Issue description

https://cs.corp.google.com/chromeos_public/src/third_party/autotest/files/client/site_tests/graphics_Idle/graphics_Idle.py?l=45

We should get rid of the logged_in=false param. Once upon a time the logged in browser was not stable which is when guest mode was used for this test, but that's no longer true.
 

Comment 1 by ihf@chromium.org, Jan 4 2018

Could you please elaborate, because I don't see a particular reason for this proposal.
Guest mode recently broke, for eg:
https://uberchromegw.corp.google.com/i/chromeos.chrome/builders/tricky-tot-chrome-pfq-informational/builds/7545

The failing tests are security_ProfilePermissions.guest, login_CryptohomeIncognito, and graphics_Idle. The first 2 pretty clearly exercise guest mode, but graphics_Idle only uses it for historical reasons from a long bygone era. I think it's better to be consistent with other autotests and use the normal browser. 

You can see that this behavior confuses people:
https://bugs.chromium.org/p/chromium/issues/detail?id=797620#c40

Status: Assigned (was: Untriaged)

Sign in to add a comment