|
|
DescriptionDon't record Signin_Signin_From* user actions for re-auth, unlock and adding secondary account
This CL also fixes the bug in CL https://codereview.chromium.org/2384233002/
BUG=632052
CQ_INCLUDE_TRYBOTS=master.tryserver.chromium.linux:closure_compilation
Committed: https://crrev.com/e24072b0a38056ab3eb09d032b24addcfc69ac23
Cr-Commit-Position: refs/heads/master@{#425036}
Patch Set 1 #
Total comments: 2
Messages
Total messages: 23 (16 generated)
Description was changed from ========== format fix BUG= ========== to ========== format fix BUG= CQ_INCLUDE_TRYBOTS=master.tryserver.chromium.linux:closure_compilation ==========
Description was changed from ========== format fix BUG= CQ_INCLUDE_TRYBOTS=master.tryserver.chromium.linux:closure_compilation ========== to ========== Don't record Signin_Signin_From* user actions for re-auth, unlock and adding secondary account BUG=632052 CQ_INCLUDE_TRYBOTS=master.tryserver.chromium.linux:closure_compilation ==========
Description was changed from ========== Don't record Signin_Signin_From* user actions for re-auth, unlock and adding secondary account BUG=632052 CQ_INCLUDE_TRYBOTS=master.tryserver.chromium.linux:closure_compilation ========== to ========== Don't record Signin_Signin_From* user actions for re-auth, unlock and adding secondary account This CL also fixes the bug in CL https://codereview.chromium.org/2384233002/ BUG=632052 CQ_INCLUDE_TRYBOTS=master.tryserver.chromium.linux:closure_compilation ==========
The CQ bit was checked by gogerald@chromium.org to run a CQ dry run
Dry run: CQ is trying da patch. Follow status at https://chromium-cq-status.appspot.com/v2/patch-status/codereview.chromium.or...
gogerald@chromium.org changed reviewers: + rogerta@chromium.org
Hi, PTAL,
The CQ bit was unchecked by commit-bot@chromium.org
Dry run: Try jobs failed on following builders: ios-simulator on master.tryserver.chromium.mac (JOB_FAILED, http://build.chromium.org/p/tryserver.chromium.mac/builders/ios-simulator/bui...)
lgtm, one question below. https://codereview.chromium.org/2411883002/diff/1/chrome/browser/ui/webui/sig... File chrome/browser/ui/webui/signin/inline_login_handler.cc (right): https://codereview.chromium.org/2411883002/diff/1/chrome/browser/ui/webui/sig... chrome/browser/ui/webui/signin/inline_login_handler.cc:203: reason != signin_metrics::Reason::REASON_ADD_SECONDARY_ACCOUNT) { Instead of checking for not reauth|unlock|add-secondary, would it be better to check explicitly for REASON_SIGNIN_PRIMARY_ACCOUNT? I ask because currently if the reason is REASON_UNKNOWN_REASON we will record metrics, and I'm not sure if we want to or not.
gogerald@chromium.org changed reviewers: + bauerb@chromium.org
bauerb@chromium.org: Please review changes in */inline_login.js https://codereview.chromium.org/2411883002/diff/1/chrome/browser/ui/webui/sig... File chrome/browser/ui/webui/signin/inline_login_handler.cc (right): https://codereview.chromium.org/2411883002/diff/1/chrome/browser/ui/webui/sig... chrome/browser/ui/webui/signin/inline_login_handler.cc:203: reason != signin_metrics::Reason::REASON_ADD_SECONDARY_ACCOUNT) { On 2016/10/12 15:16:45, Roger Tawa wrote: > Instead of checking for not reauth|unlock|add-secondary, would it be better to > check explicitly for REASON_SIGNIN_PRIMARY_ACCOUNT? I ask because currently if > the reason is REASON_UNKNOWN_REASON we will record metrics, and I'm not sure if > we want to or not. I think we might have to record it since if the reason is REASON_UNKNOWN_REASON we will sign in the account as primary account, like here https://cs.chromium.org/chromium/src/chrome/browser/ui/webui/signin/inline_lo...
The CQ bit was checked by gogerald@chromium.org to run a CQ dry run
Dry run: CQ is trying da patch. Follow status at https://chromium-cq-status.appspot.com/v2/patch-status/codereview.chromium.or...
The CQ bit was unchecked by commit-bot@chromium.org
Dry run: Try jobs failed on following builders: ios-simulator on master.tryserver.chromium.mac (JOB_FAILED, http://build.chromium.org/p/tryserver.chromium.mac/builders/ios-simulator/bui...)
lgtm
The CQ bit was checked by gogerald@chromium.org
CQ is trying da patch. Follow status at https://chromium-cq-status.appspot.com/v2/patch-status/codereview.chromium.or...
Message was sent while issue was closed.
Description was changed from ========== Don't record Signin_Signin_From* user actions for re-auth, unlock and adding secondary account This CL also fixes the bug in CL https://codereview.chromium.org/2384233002/ BUG=632052 CQ_INCLUDE_TRYBOTS=master.tryserver.chromium.linux:closure_compilation ========== to ========== Don't record Signin_Signin_From* user actions for re-auth, unlock and adding secondary account This CL also fixes the bug in CL https://codereview.chromium.org/2384233002/ BUG=632052 CQ_INCLUDE_TRYBOTS=master.tryserver.chromium.linux:closure_compilation ==========
Message was sent while issue was closed.
Committed patchset #1 (id:1)
Message was sent while issue was closed.
Description was changed from ========== Don't record Signin_Signin_From* user actions for re-auth, unlock and adding secondary account This CL also fixes the bug in CL https://codereview.chromium.org/2384233002/ BUG=632052 CQ_INCLUDE_TRYBOTS=master.tryserver.chromium.linux:closure_compilation ========== to ========== Don't record Signin_Signin_From* user actions for re-auth, unlock and adding secondary account This CL also fixes the bug in CL https://codereview.chromium.org/2384233002/ BUG=632052 CQ_INCLUDE_TRYBOTS=master.tryserver.chromium.linux:closure_compilation Committed: https://crrev.com/e24072b0a38056ab3eb09d032b24addcfc69ac23 Cr-Commit-Position: refs/heads/master@{#425036} ==========
Message was sent while issue was closed.
Patchset 1 (id:??) landed as https://crrev.com/e24072b0a38056ab3eb09d032b24addcfc69ac23 Cr-Commit-Position: refs/heads/master@{#425036} |