Convert DLOG/DVLOG messages in chrome.dial to VLOG.

Convert DLOG/DVLOG messages in chrome.dial to VLOG.

Messages which track the progress of discovery are VLOG(2) and unusual events are VLOG(1).

We can use this to diagnose failures in test automation with release builds.

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

[Wez, 2014-07-17 00:39:01]

lgtm

https://codereview.chromium.org/394383002/diff/1/chrome/browser/extensions/ap...
File chrome/browser/extensions/api/dial/dial_service.cc (right):

https://codereview.chromium.org/394383002/diff/1/chrome/browser/extensions/ap...
chrome/browser/extensions/api/dial/dial_service.cc:331: VLOG(2) << "raw_headers:
" << raw_headers << "\n";
nit: Should this even be VLOG(3), perhaps, since it's likely to be verbose?

[mark a. foltz, 2014-07-17 18:33:20]

https://codereview.chromium.org/394383002/diff/1/chrome/browser/extensions/ap...
File chrome/browser/extensions/api/dial/dial_service.cc (right):

https://codereview.chromium.org/394383002/diff/1/chrome/browser/extensions/ap...
chrome/browser/extensions/api/dial/dial_service.cc:331: VLOG(2) << "raw_headers:
" << raw_headers << "\n";
On 2014/07/17 00:39:01, Wez wrote:
> nit: Should this even be VLOG(3), perhaps, since it's likely to be verbose?

Done.

[mark a. foltz, 2014-07-17 18:34:09]

The CQ bit was checked by mfoltz@chromium.org

[commit-bot: I haz the power, 2014-07-17 18:38:05]

CQ is trying da patch. Follow status at
 https://chromium-status.appspot.com/cq/mfoltz@chromium.org/394383002/20001

[commit-bot: I haz the power, 2014-07-17 22:18:29]

FYI, CQ is re-trying this CL (attempt #1).
The failing builders are:
  android_dbg_triggered_tests on tryserver.chromium
(http://build.chromium.org/p/tryserver.chromium/builders/android_dbg_triggered...)
  mac_gpu_triggered_tests on tryserver.chromium.gpu
(http://build.chromium.org/p/tryserver.chromium.gpu/builders/mac_gpu_triggered...)

[commit-bot: I haz the power, 2014-07-17 23:30:05]

Change committed as 283924