Re-reenable memory tests. Fixed sign-in issue.

Re-reenable memory tests. Fixed sign-in issue. Added missing recording.

BUG=370977
Committed: https://crrev.com/435610515900bb7875eeea87366ff6cfd8d91634
Cr-Commit-Position: refs/heads/master@{#292639}

[Victor Starodub, 2014-08-29 13:31:31]

starodub@google.com changed reviewers:
+ marja@chromium.org

[marja, 2014-08-29 13:41:33]

Is this exactly the same as https://codereview.chromium.org/491863003 or what's
the difference?

[Victor Starodub, 2014-08-29 13:47:19]

On 2014/08/29 13:41:33, marja wrote:
> Is this exactly the same as https://codereview.chromium.org/491863003 or
what's
> the difference?

It has the new recording hash. The old one was submitted (and reverted) without
one.

I messed up my git branches and though it would be easier to start a new one
rather that reverting the revert and adding a hash to it.

[marja, 2014-08-29 13:56:19]

Rubberstamp lgtm, since skyostil@ has already reviewed an equivalent CL.

If its easier for you, you can always revive your old CL at the tip of tree by
"git cl patch <number>". If you just want to upload a patch set to a random CL
you can associate your branch with it with "git cl issue <number>" and then just
git cl upload.

[Victor Starodub, 2014-08-29 13:58:42]

The CQ bit was checked by starodub@google.com

[commit-bot: I haz the power, 2014-08-29 13:59:25]

CQ is trying da patch. Follow status at
 https://chromium-status.appspot.com/cq/starodub@google.com/520683002/1

[commit-bot: I haz the power, 2014-08-29 15:29:30]

Committed patchset #1 (id:1) as 0d7bf70f4683128a009370a2161a0d4b23fe0507

[commit-bot: I haz the power, 2014-09-10 03:08:50]

Patchset 1 (id:??) landed as
https://crrev.com/435610515900bb7875eeea87366ff6cfd8d91634
Cr-Commit-Position: refs/heads/master@{#292639}