Issue 239212 in chromium: Better error reporting when --auth-ext-path is not readable

[chro...@googlecode.com]

Status: Assigned
Owner: te...@chromium.org
CC: ach...@chromium.org
Labels: Type-Bug Pri-2 Cr-Tests-Telemetry OS-Chrome

New issue 239212 by ach...@chromium.org: Better error reporting when
--auth-ext-path is not readable
http://code.google.com/p/chromium/issues/detail?id=239212

Right now, if you point --auth-ext-path to a location that doesn't exist or
chrome doesn't have permission to read the directory, we have a silent
failure that's difficult to debug. At a minimum, we should print something
in the log. Ideally we should surface an error in the oobe screen so it's
more obvious what happened. This has already wasted a bunch of time
(especially when the login extension directory is created by root on the
device).

--
You received this message because this project is configured to send all
issue notifications to this address.
You may adjust your notification preferences at:
https://code.google.com/hosting/settings

[chro...@googlecode.com]

Updates:
Status: Started

Comment #3 on issue 239212 by ach...@chromium.org: Better error reporting

when --auth-ext-path is not readable
http://code.google.com/p/chromium/issues/detail?id=239212

The error reporting should be in chrome, not in telemetry.

[chro...@googlecode.com]

Updates:
Labels: Iteration-82

Comment #4 on issue 239212 by zeli...@chromium.org: Better error reporting

when --auth-ext-path is not readable
http://code.google.com/p/chromium/issues/detail?id=239212

(No comment was entered for this change.)

[chro...@googlecode.com]

Comment #5 on issue 239212 by bugdro...@chromium.org: Better error

reporting when --auth-ext-path is not readable

http://code.google.com/p/chromium/issues/detail?id=239212#c5

------------------------------------------------------------------------
r201928 | te...@chromium.org | 2013-05-23T23:36:01.146106Z

Changed paths:
M
http://src.chromium.org/viewvc/chrome/trunk/src/tools/telemetry/telemetry/core/chrome/cros_util.py?r1=201928&r2=201927&pathrev=201928

Make cros login error message more descriptive.

When a telemetry test fails to login the test user, the most likely cause
is a failure to load the login extension. It is difficult to identify this
problem with the old generic timeout error message.

BUG=239212
TEST=run_tests with bad --auth-ext-path flag on cros
NOTRY=true

Review URL: https://chromiumcodereview.appspot.com/15747016
------------------------------------------------------------------------

[chro...@googlecode.com]

Updates:
Status: Assigned

Comment #9 on issue 239212 by te...@chromium.org: Better error reporting

when --auth-ext-path is not readable
http://code.google.com/p/chromium/issues/detail?id=239212

Revision 202926 was reverted since it broke the login autotests. I'll
investigate why this is happening.