Move fullscreen_controller browser tests to interactive.

Move fullscreen_controller browser tests to interactive.


BUG=146665
Committed: http://src.chromium.org/viewvc/chrome?view=rev&revision=155422

[Robert Sesek, 2012-09-06 18:20:51]

https://chromiumcodereview.appspot.com/10919113/diff/5003/chrome/browser/ui/f...
File
chrome/browser/ui/fullscreen/fullscreen_controller_interactive_browsertest.cc
(right):

https://chromiumcodereview.appspot.com/10919113/diff/5003/chrome/browser/ui/f...
chrome/browser/ui/fullscreen/fullscreen_controller_interactive_browsertest.cc:170:
} while (retry_until_success &&
Is this part still necessary since these tests won't run in parallel?

[scheib, 2012-09-06 20:55:02]

https://chromiumcodereview.appspot.com/10919113/diff/5003/chrome/browser/ui/f...
File
chrome/browser/ui/fullscreen/fullscreen_controller_interactive_browsertest.cc
(right):

https://chromiumcodereview.appspot.com/10919113/diff/5003/chrome/browser/ui/f...
chrome/browser/ui/fullscreen/fullscreen_controller_interactive_browsertest.cc:170:
} while (retry_until_success &&
On 2012/09/06 18:20:51, rsesek wrote:
> Is this part still necessary since these tests won't run in parallel?

ToggleFullscreenModeForTab tests using this code without the loop, and
unfortunately was still flaky even in interactive tests. http://crbug.com/133831
is in place to track this. I was planning to wait for the Fullscreen Controller
overhaul before attempting to enable this test again.

[Robert Sesek, 2012-09-07 15:12:43]

lgtm

[scheib, 2012-09-07 15:28:14]

sky, owner review please.

[sky, 2012-09-07 16:17:36]

LGTM

[commit-bot: I haz the power, 2012-09-07 16:26:16]

CQ is trying da patch. Follow status at
https://chromium-status.appspot.com/cq/scheib@chromium.org/10919113/5003

[commit-bot: I haz the power, 2012-09-07 18:01:27]

Change committed as 155422