Setting AudioOutputDevice authorization timeout to 1000ms

Setting AudioOutputDevice authorization timeout to 1000ms

There is an ongoing discussion in https://codereview.chromium.org/2121223002/
regarding timeout values and UMA stats for those. Meanwhile, increasing the timeout from 900ms to 1000ms
since 900ms is too strict: according to the latest UMA stats 0.4% of authorizations time out.

Landing this will allow us to gather some stats at least.

BUG=615589
Committed: https://crrev.com/bd9ad97e1da5d2084b76ea929ab755902922d9fc
Cr-Commit-Position: refs/heads/master@{#404399}

[o1ka, 2016-07-08 12:16:01]

olka@chromium.org changed reviewers:
+ tommi@chromium.org

[o1ka, 2016-07-08 12:16:01]

Tommi, PTAL

[o1ka, 2016-07-08 12:16:35]

Description was changed from

==========
Setting  AudioOutputDevice authorization timeout to 1000ms

There is an ongoig discussion in https://codereview.chromium.org/2121223002/
reguarding timeout values and UMA stats for those. Meanwhile, increasing timeout
from 900ms to 1000ms
since 900ms is too strict: according to latest UMA stats 0.4% of authorizations
time out.

BUG=615589
==========

to

==========
Setting  AudioOutputDevice authorization timeout to 1000ms

There is an ongoig discussion in https://codereview.chromium.org/2121223002/
reguarding timeout values and UMA stats for those. Meanwhile, increasing timeout
from 900ms to 1000ms
since 900ms is too strict: according to latest UMA stats 0.4% of authorizations
time out.

Landing this will allow us to gather some stats at least.

BUG=615589
==========

[tommi (sloooow) - chröme, 2016-07-08 13:16:24]

Description was changed from

==========
Setting  AudioOutputDevice authorization timeout to 1000ms

There is an ongoig discussion in https://codereview.chromium.org/2121223002/
reguarding timeout values and UMA stats for those. Meanwhile, increasing timeout
from 900ms to 1000ms
since 900ms is too strict: according to latest UMA stats 0.4% of authorizations
time out.

Landing this will allow us to gather some stats at least.

BUG=615589
==========

to

==========
Setting  AudioOutputDevice authorization timeout to 1000ms

There is an ongoing discussion in https://codereview.chromium.org/2121223002/
regarding timeout values and UMA stats for those. Meanwhile, increasing the
timeout from 900ms to 1000ms
since 900ms is too strict: according to the latest UMA stats 0.4% of
authorizations time out.

Landing this will allow us to gather some stats at least.

BUG=615589
==========

[tommi (sloooow) - chröme, 2016-07-08 13:16:30]

lgtm

[tommi (sloooow) - chröme, 2016-07-08 13:16:45]

Description was changed from

==========
Setting  AudioOutputDevice authorization timeout to 1000ms

There is an ongoing discussion in https://codereview.chromium.org/2121223002/
regarding timeout values and UMA stats for those. Meanwhile, increasing the
timeout from 900ms to 1000ms
since 900ms is too strict: according to the latest UMA stats 0.4% of
authorizations time out.

Landing this will allow us to gather some stats at least.

BUG=615589
==========

to

==========
Setting AudioOutputDevice authorization timeout to 1000ms

There is an ongoing discussion in https://codereview.chromium.org/2121223002/
regarding timeout values and UMA stats for those. Meanwhile, increasing the
timeout from 900ms to 1000ms
since 900ms is too strict: according to the latest UMA stats 0.4% of
authorizations time out.

Landing this will allow us to gather some stats at least.

BUG=615589
==========

[o1ka, 2016-07-08 13:22:21]

The CQ bit was checked by olka@chromium.org

[commit-bot: I haz the power, 2016-07-08 13:23:13]

CQ is trying da patch. Follow status at
 
https://chromium-cq-status.appspot.com/v2/patch-status/codereview.chromium.or...

[commit-bot: I haz the power, 2016-07-08 15:56:03]

Description was changed from

==========
Setting AudioOutputDevice authorization timeout to 1000ms

There is an ongoing discussion in https://codereview.chromium.org/2121223002/
regarding timeout values and UMA stats for those. Meanwhile, increasing the
timeout from 900ms to 1000ms
since 900ms is too strict: according to the latest UMA stats 0.4% of
authorizations time out.

Landing this will allow us to gather some stats at least.

BUG=615589
==========

to

==========
Setting AudioOutputDevice authorization timeout to 1000ms

There is an ongoing discussion in https://codereview.chromium.org/2121223002/
regarding timeout values and UMA stats for those. Meanwhile, increasing the
timeout from 900ms to 1000ms
since 900ms is too strict: according to the latest UMA stats 0.4% of
authorizations time out.

Landing this will allow us to gather some stats at least.

BUG=615589
==========

[commit-bot: I haz the power, 2016-07-08 15:56:04]

Committed patchset #1 (id:1)

[commit-bot: I haz the power, 2016-07-08 15:56:11]

CQ bit was unchecked.

[commit-bot: I haz the power, 2016-07-08 15:57:30]

Description was changed from

==========
Setting AudioOutputDevice authorization timeout to 1000ms

There is an ongoing discussion in https://codereview.chromium.org/2121223002/
regarding timeout values and UMA stats for those. Meanwhile, increasing the
timeout from 900ms to 1000ms
since 900ms is too strict: according to the latest UMA stats 0.4% of
authorizations time out.

Landing this will allow us to gather some stats at least.

BUG=615589
==========

to

==========
Setting AudioOutputDevice authorization timeout to 1000ms

There is an ongoing discussion in https://codereview.chromium.org/2121223002/
regarding timeout values and UMA stats for those. Meanwhile, increasing the
timeout from 900ms to 1000ms
since 900ms is too strict: according to the latest UMA stats 0.4% of
authorizations time out.

Landing this will allow us to gather some stats at least.

BUG=615589

Committed: https://crrev.com/bd9ad97e1da5d2084b76ea929ab755902922d9fc
Cr-Commit-Position: refs/heads/master@{#404399}
==========

[commit-bot: I haz the power, 2016-07-08 15:57:31]

Patchset 1 (id:??) landed as
https://crrev.com/bd9ad97e1da5d2084b76ea929ab755902922d9fc
Cr-Commit-Position: refs/heads/master@{#404399}