Enable bluetooth on chromeos, win, and mac, but disable on linux unless in the whitelist. The white…

Enable bluetooth on chromeos, win, and mac, but disable on linux unless in the whitelist. The whitelist includes the HotRod apps.

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

[keybuk, 2014-07-22 17:38:51]

lgtm to me in principle, but kalman must review

[not at google - send to devlin, 2014-07-22 17:43:19]

lgtm

[Alan Savage, 2014-07-22 17:50:39]

The CQ bit was checked by asavage@chromium.org

[commit-bot: I haz the power, 2014-07-22 17:52:05]

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

[commit-bot: I haz the power, 2014-07-22 20:58:54]

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

[commit-bot: I haz the power, 2014-07-22 21:46:25]

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

[commit-bot: I haz the power, 2014-07-22 21:46:26]

Try jobs failed on following builders:
  linux_chromium_rel_swarming on tryserver.chromium
(http://build.chromium.org/p/tryserver.chromium/builders/linux_chromium_rel_sw...)

[Alan Savage, 2014-07-22 22:15:02]

On 2014/07/22 21:46:26, I haz the power (commit-bot) wrote:
> Try jobs failed on following builders:
>   linux_chromium_rel_swarming on tryserver.chromium
>
(http://build.chromium.org/p/tryserver.chromium/builders/linux_chromium_rel_sw...)

How can I disable the linux tests for this API or add them to the whitelist?

[not at google - send to devlin, 2014-07-22 23:53:57]

On 2014/07/22 22:15:02, Alan Savage wrote:
> On 2014/07/22 21:46:26, I haz the power (commit-bot) wrote:
> > Try jobs failed on following builders:
> >   linux_chromium_rel_swarming on tryserver.chromium
> >
>
(http://build.chromium.org/p/tryserver.chromium/builders/linux_chromium_rel_sw...)
> 
> How can I disable the linux tests for this API or add them to the whitelist?

To add to the whitelist you need to get a stable ID for those extensions, then
add that stable ID to the whitelist. The latter is easy of course. The former
you need to load up one of the extensions, then
1. note its ID
2. note the value for "key" it gets in Preferences
3. add that ID to the whitelist
4. manually set that "key" in every test extension's manifest

of course this means that you'd end up getting the same extension ID for every
extension, so don't try to install more than one of them at a time.

[Alan Savage, 2014-07-25 18:51:03]

PTAL All failing tests now pass locally. I don't have try-bot access (request
pending approval).

[armansito, 2014-07-25 22:47:34]

lgtm. Please wait for kalman@ to approve the latest patch set as well.

[not at google - send to devlin, 2014-07-25 22:50:04]

lgtm

[Alan Savage, 2014-07-26 19:43:10]

The CQ bit was checked by asavage@chromium.org

[commit-bot: I haz the power, 2014-07-26 19:44:25]

CQ is trying da patch. Follow status at
 https://chromium-status.appspot.com/cq/asavage@chromium.org/406293002/40001

[commit-bot: I haz the power, 2014-07-26 23:22:31]

Change committed as 285816