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

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

Re-recording other tests may be required.

BUG=370977
Committed: https://crrev.com/703621781308560423bc1792edf662bb85c7afdc
Cr-Commit-Position: refs/heads/master@{#292168}

[Victor Starodub, 2014-08-22 11:34:01]

Please take a look. Is there any way to try this change before submitting? I'm
worried that I might break google sign-in for other tests.

[Sami, 2014-08-22 12:28:14]

Fix looks correct, but can you make sure the hash for the new recording gets
added too. Probably need to try this on the bots to see what breaks.

https://codereview.chromium.org/491863003/diff/1/tools/perf/page_sets/data/mo...
File tools/perf/page_sets/data/mobile_memory.json (right):

https://codereview.chromium.org/491863003/diff/1/tools/perf/page_sets/data/mo...
tools/perf/page_sets/data/mobile_memory.json:4: "mobile_memory_018.wpr": [
Looks like the sha1 file for this file is missing from the patch.

[Victor Starodub, 2014-08-26 11:54:37]

Couldn't find any other failing tests. Seems like the sign-in portion of the
test is used mostly with '--use-live-sites'

https://codereview.chromium.org/491863003/diff/1/tools/perf/page_sets/data/mo...
File tools/perf/page_sets/data/mobile_memory.json (right):

https://codereview.chromium.org/491863003/diff/1/tools/perf/page_sets/data/mo...
tools/perf/page_sets/data/mobile_memory.json:4: "mobile_memory_018.wpr": [
On 2014/08/22 12:28:13, Sami wrote:
> Looks like the sha1 file for this file is missing from the patch.

Done.

[Victor Starodub, 2014-08-26 11:55:08]

The CQ bit was checked by starodub@google.com

[Victor Starodub, 2014-08-26 11:55:09]

The CQ bit was unchecked by starodub@google.com

[Victor Starodub, 2014-08-26 11:56:07]

The CQ bit was checked by starodub@google.com

[commit-bot: I haz the power, 2014-08-26 11:56:54]

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

[commit-bot: I haz the power, 2014-08-26 11:56:55]

The CQ bit was unchecked by commit-bot@chromium.org

[commit-bot: I haz the power, 2014-08-26 11:56:56]

No LGTM from a valid reviewer yet. Only full committers are accepted.
Even if an LGTM may have been provided, it was from a non-committer or
a provisional committer, _not_ a full super star committer.
See http://www.chromium.org/getting-involved/become-a-committer
Note that this has nothing to do with OWNERS files.

[Sami, 2014-08-26 12:01:15]

lgtm.

[Victor Starodub, 2014-08-26 13:14:35]

The CQ bit was checked by starodub@google.com

[commit-bot: I haz the power, 2014-08-26 13:15:37]

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

[commit-bot: I haz the power, 2014-08-26 14:13:53]

FYI, CQ is re-trying this CL (attempt #1).
The failing builders are:
  chromium_presubmit on tryserver.chromium.linux
(http://build.chromium.org/p/tryserver.chromium.linux/builders/chromium_presub...)
  linux_chromium_rel_swarming on tryserver.chromium.linux
(http://build.chromium.org/p/tryserver.chromium.linux/builders/linux_chromium_...)
  mac_chromium_rel_swarming on tryserver.chromium.mac
(http://build.chromium.org/p/tryserver.chromium.mac/builders/mac_chromium_rel_...)
  win_chromium_rel_swarming on tryserver.chromium.win
(http://build.chromium.org/p/tryserver.chromium.win/builders/win_chromium_rel_...)
  win_chromium_x64_rel_swarming on tryserver.chromium.win
(http://build.chromium.org/p/tryserver.chromium.win/builders/win_chromium_x64_...)

[commit-bot: I haz the power, 2014-08-26 14:17:45]

The CQ bit was unchecked by commit-bot@chromium.org

[commit-bot: I haz the power, 2014-08-26 14:17:46]

Try jobs failed on following builders:
  chromium_presubmit on tryserver.chromium.linux
(http://build.chromium.org/p/tryserver.chromium.linux/builders/chromium_presub...)

[Victor Starodub, 2014-08-27 14:57:03]

The CQ bit was checked by starodub@google.com

[commit-bot: I haz the power, 2014-08-27 14:57:57]

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

[commit-bot: I haz the power, 2014-08-27 15:56:34]

FYI, CQ is re-trying this CL (attempt #1).
The failing builders are:
  linux_gpu_triggered_tests on tryserver.chromium.gpu
(http://build.chromium.org/p/tryserver.chromium.gpu/builders/linux_gpu_trigger...)
  win_chromium_x64_rel_swarming on tryserver.chromium.win
(http://build.chromium.org/p/tryserver.chromium.win/builders/win_chromium_x64_...)

[commit-bot: I haz the power, 2014-08-27 16:56:04]

Committed patchset #3 (id:40001) as 383ffaab6b5fac34b950d9faaab637cc75907aca

[tonyg, 2014-08-27 23:10:38]

A revert of this CL (patchset #3) has been created in
https://codereview.chromium.org/511023002/ by tonyg@chromium.org.

The reason for reverting is: Failing on bots. Looks like we forgot to commit the
archive.

Traceback (most recent call last):
  File
"/b/build/slave/Android_Nexus5_Perf/build/src/tools/perf/../telemetry/telemetry/value/failure.py",
line 39, in _GetExcInfoFromMessage
    raise Exception(message)
Exception: Page set archive doesn't exist.

http://chromegw/i/chromium.perf/builders/Android%20Nexus5%20Perf/builds/1480/....

[commit-bot: I haz the power, 2014-09-10 02:52:13]

Patchset 4 (id:??) landed as
https://crrev.com/703621781308560423bc1792edf662bb85c7afdc
Cr-Commit-Position: refs/heads/master@{#292168}