telemetry: re-enable befamous in key_silk_cases.

telemetry: re-enable befamous in key_silk_cases.

The page works fine on ToT. Looks like the scrolling problem has been fixed.

R=tonyg@chromium.org
BUG=366371
Committed: https://src.chromium.org/viewvc/chrome?view=rev&revision=270918

[ernstm, 2014-05-15 22:43:48]

PTAL

[dtu, 2014-05-15 23:17:05]

lgtm

[ernstm, 2014-05-15 23:37:35]

The CQ bit was checked by ernstm@chromium.org

[commit-bot: I haz the power, 2014-05-15 23:39:11]

CQ is trying da patch. Follow status at
 https://chromium-status.appspot.com/cq/ernstm@chromium.org/288033011/1

[commit-bot: I haz the power, 2014-05-16 02:12:55]

FYI, CQ is re-trying this CL (attempt #1).
Please consider checking whether the failures are real,
and report flakes to chrome-troopers@google.com.
The failing builders are:
  win_chromium_x64_rel on tryserver.chromium
(http://build.chromium.org/p/tryserver.chromium/builders/win_chromium_x64_rel/...)

[commit-bot: I haz the power, 2014-05-16 03:26:55]

Change committed as 270918

[tonyg, 2014-05-16 09:19:10]

On 2014/05/16 03:26:55, I haz the power (commit-bot) wrote:
> Change committed as 270918

We probably should have added a unittest of some sort that would have caught the
failure that triggered this to be disabled.  Perhaps something for a follow-up?

[ernstm, 2014-05-16 20:27:40]

On 2014/05/16 09:19:10, tonyg wrote:
> On 2014/05/16 03:26:55, I haz the power (commit-bot) wrote:
> > Change committed as 270918
> 
> We probably should have added a unittest of some sort that would have caught
the
> failure that triggered this to be disabled.  Perhaps something for a
follow-up?

The page didn't scroll. It is not possible to detect that in all cases:
https://code.google.com/p/chromium/issues/detail?id=360204#c7