More non-debug logging in Chrome Frame tests.

More non-debug logging in Chrome Frame tests.

There are only good reasons to not use DLOG and DVLOG in test code.

Also, avoid a potential race by setting up ChromeFrameTestWithWebServer expectations before launching the browser.

BUG=none
TEST=none

Committed: https://src.chromium.org/viewvc/chrome?view=rev&revision=128638

[robertshield, 2012-03-23 16:57:33]

On 2012/03/23 15:26:50, grt wrote:

LGTM++

[commit-bot: I haz the power, 2012-03-23 17:10:00]

CQ is trying da patch. Follow status at
https://chromium-status.appspot.com/cq/grt@chromium.org/9838058/3001

[commit-bot: I haz the power, 2012-03-23 21:23:52]

Try job failure for 9838058-3001 (retry) on mac_rel for step "browser_tests".
It's a second try, previously, steps "ui_tests, browser_tests" failed.
http://build.chromium.org/p/tryserver.chromium/buildstatus?builder=mac_rel&nu...

[commit-bot: I haz the power, 2012-03-23 21:44:50]

CQ is trying da patch. Follow status at
https://chromium-status.appspot.com/cq/grt@chromium.org/9838058/3001