Re-enable gtalk test.

Re-enable gtalk test. Wait until mole content loads before trying to disable extension. Test was occasionally hitting errors when disabling the extension because it could not get the window.
BUG=128563
Committed: http://src.chromium.org/viewvc/chrome?view=rev&revision=141153

[krenaud, 2012-06-05 22:09:38]

Re-adding gtalk pyauto test to suite.

[Nirnimesh, 2012-06-05 23:58:36]

Are you sure the problems have been fixed now? The test was very flaky when it
was disabled. Are you confident it won't be flaky anymore?

[krenaud, 2012-06-06 00:18:10]

On 2012/06/05 23:58:36, Nirnimesh wrote:
> Are you sure the problems have been fixed now? The test was very flaky when it
> was disabled. Are you confident it won't be flaky anymore?

I ran the test locally many times and did not see issues. I also ran on Mac QA
machine last week and did not see flaky failures. Is there some way to run the
test across all of the configs many times before submitting?

[Nirnimesh, 2012-06-06 00:29:27]

I'm fine if you want to try on the bots again.
LGTM.

[craigdh, 2012-06-06 00:35:38]

lgtm, but let's keep an eye on it and revert if it starts flaking.

[krenaud, 2012-06-07 18:12:03]

Made small change to the test. This seems to fix the flakiness issue. Please
review.

[Nirnimesh, 2012-06-07 18:16:52]

Sleep is a bad idea. While it might seem to fix flakiness, it's no guarantee and
you'll see flakiness on a slower machine. Please wait for the right thing to
happen instead of a blanket sleep

[krenaud, 2012-06-07 18:27:08]

Agreed. What this sleep was actually doing was giving time for the window to
fully appear. Now I check that the mole content is loaded before trying to
disable the extension.

[Nirnimesh, 2012-06-07 18:40:20]

LGTM

[craigdh, 2012-06-07 18:41:21]

lgtm, thanks for fixing the source of the flakiness.

[commit-bot: I haz the power, 2012-06-07 18:41:45]

CQ is trying da patch. Follow status at
https://chromium-status.appspot.com/cq/krenaud@google.com/10535022/7001

[commit-bot: I haz the power, 2012-06-07 20:28:35]

Try job failure for 10535022-7001 (retry) on win for step "compile" (clobber
build).
It's a second try, previously, step "compile" failed.
http://build.chromium.org/p/tryserver.chromium/buildstatus?builder=win&number...

[commit-bot: I haz the power, 2012-06-08 00:36:26]

CQ is trying da patch. Follow status at
https://chromium-status.appspot.com/cq/krenaud@google.com/10535022/7001

[commit-bot: I haz the power, 2012-06-08 01:52:01]

Change committed as 141153