bluetooth: update bluetooth_dispatcher_host VLOG to BLUETOOTH_LOG

bluetooth: update bluetooth_dispatcher_host VLOG to BLUETOOTH_LOG

BUG=516825

[fbeaufortchromium, 2016-01-27 14:24:25]

fbeaufort@chromium.org changed reviewers:
+ fbeaufort@chromium.org, ortuno@chromium.org

[fbeaufortchromium, 2016-01-27 14:24:25]

@ortuno please have a look ;)

[ortuno, 2016-01-27 19:15:36]

ortuno@chromium.org changed reviewers:
+ scheib@chromium.org

[ortuno, 2016-01-27 19:15:36]

These look good to me. Adding scheib since he might have some concerns.

https://codereview.chromium.org/1639293002/diff/1/content/browser/bluetooth/b...
File content/browser/bluetooth/bluetooth_dispatcher_host.cc (right):

https://codereview.chromium.org/1639293002/diff/1/content/browser/bluetooth/b...
content/browser/bluetooth/bluetooth_dispatcher_host.cc:81: return false;
Hmm I wonder if we should log these so that we know why a device isn't showing
up for someone.

https://codereview.chromium.org/1639293002/diff/1/content/browser/bluetooth/b...
content/browser/bluetooth/bluetooth_dispatcher_host.cc:81: return false;
Hmm I wonder if we should log these so that we know why a device isn't showing
up for someone.

https://codereview.chromium.org/1639293002/diff/1/content/browser/bluetooth/b...
content/browser/bluetooth/bluetooth_dispatcher_host.cc:468: for
(IDMap<RequestDeviceSession, IDMapOwnPointer>::iterator iter(
Can you add a log statement here? Something like: Stopping discovery session.

[scheib, 2016-01-27 21:52:01]

LGTM

[fbeaufortchromium, 2016-01-28 08:46:51]

fbeaufort@chromium.org changed reviewers:
+ pfeldman@chromium.org

[fbeaufortchromium, 2016-01-28 08:46:52]

pfeldman@chromium.org: Please review changes in 
content/DEPS
content/browser/BUILD.gn

ortuno@chromium.org: I've addressed your feedback.

https://codereview.chromium.org/1639293002/diff/1/content/browser/bluetooth/b...
File content/browser/bluetooth/bluetooth_dispatcher_host.cc (right):

https://codereview.chromium.org/1639293002/diff/1/content/browser/bluetooth/b...
content/browser/bluetooth/bluetooth_dispatcher_host.cc:81: return false;
On 2016/01/27 19:15:36, ortuno wrote:
> Hmm I wonder if we should log these so that we know why a device isn't showing
> up for someone.

I've added BLUETOOTH_LOG(DEBUG) for all filters.

https://codereview.chromium.org/1639293002/diff/1/content/browser/bluetooth/b...
content/browser/bluetooth/bluetooth_dispatcher_host.cc:468: for
(IDMap<RequestDeviceSession, IDMapOwnPointer>::iterator iter(
On 2016/01/27 19:15:36, ortuno wrote:
> Can you add a log statement here? Something like: Stopping discovery session.

Done.

[fbeaufortchromium, 2016-01-28 08:48:29]

The CQ bit was checked by fbeaufort@chromium.org to run a CQ dry run

[commit-bot: I haz the power, 2016-01-28 08:49:15]

Dry run: CQ is trying da patch. Follow status at
 https://chromium-cq-status.appspot.com/patch-status/1639293002/20001
View timeline at
 https://chromium-cq-status.appspot.com/patch-timeline/1639293002/20001

[commit-bot: I haz the power, 2016-01-28 08:58:56]

The CQ bit was unchecked by commit-bot@chromium.org

[commit-bot: I haz the power, 2016-01-28 08:58:57]

Dry run: Try jobs failed on following builders:
  chromium_presubmit on tryserver.chromium.linux (JOB_FAILED,
http://build.chromium.org/p/tryserver.chromium.linux/builders/chromium_presub...)

[stevenjb, 2016-01-28 18:11:12]

stevenjb@chromium.org changed reviewers:
+ stevenjb@chromium.org

[stevenjb, 2016-01-28 18:11:13]

not lgtm. Many of these seem like they could be much too spammy. Will discuss
more in email.