Explicitly make BrowserThread::SetDelegate specific to the IO thread.

Explicitly make BrowserThread::SetDelegate specific to the IO thread.

The IO thread was already the only user and officially restricting users
of this API is required as BrowserThreadDelegates won't be compatible
with threads redirected to the TaskScheduler.

BUG=653916
Committed: https://crrev.com/90becc91928a53cd44e37dde76e3f29a9507f271
Cr-Commit-Position: refs/heads/master@{#437271}

[gab, 2016-12-07 21:45:33]

Patchset #2 (id:20001) has been deleted

[gab, 2016-12-07 21:46:48]

gab@chromium.org changed reviewers:
+ jam@chromium.org

[gab, 2016-12-07 21:46:49]

@jam PTAL, thanks

[gab, 2016-12-07 21:46:58]

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

[commit-bot: I haz the power, 2016-12-07 21:47:22]

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

[gab, 2016-12-07 21:54:28]

The CQ bit was unchecked by gab@chromium.org

[gab, 2016-12-07 21:54:39]

Description was changed from

==========
Explicitly make BrowserThread::SetDelegate specific to the IO thread.

The IO thread was already the only user and officially restricting users
of this API is required as BrowserThreadDelegates won't be compatible
with threads redirected to the TaskScheduler.

BUG=653916
==========

to

==========
Explicitly make BrowserThread::SetDelegate specific to the IO thread.

The IO thread was already the only user and officially restricting users
of this API is required as BrowserThreadDelegates won't be compatible
with threads redirected to the TaskScheduler.

BUG=653916
CQ_INCLUDE_TRYBOTS=master.tryserver.chromium.linux:linux_chromium_tsan_rel_ng
==========

[gab, 2016-12-07 21:54:45]

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

[commit-bot: I haz the power, 2016-12-07 21:55:24]

Dry run: 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-12-08 01:27:34]

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

[commit-bot: I haz the power, 2016-12-08 01:27:35]

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

[gab, 2016-12-08 13:43:29]

Description was changed from

==========
Explicitly make BrowserThread::SetDelegate specific to the IO thread.

The IO thread was already the only user and officially restricting users
of this API is required as BrowserThreadDelegates won't be compatible
with threads redirected to the TaskScheduler.

BUG=653916
CQ_INCLUDE_TRYBOTS=master.tryserver.chromium.linux:linux_chromium_tsan_rel_ng
==========

to

==========
Explicitly make BrowserThread::SetDelegate specific to the IO thread.

The IO thread was already the only user and officially restricting users
of this API is required as BrowserThreadDelegates won't be compatible
with threads redirected to the TaskScheduler.

BUG=653916
==========

[gab, 2016-12-08 13:43:36]

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

[commit-bot: I haz the power, 2016-12-08 13:43:47]

Dry run: 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-12-08 13:47:48]

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

[commit-bot: I haz the power, 2016-12-08 13:47:49]

Dry run: This issue passed the CQ dry run.

[jam, 2016-12-08 17:05:16]

lgtm

[gab, 2016-12-08 17:14:57]

The CQ bit was checked by gab@chromium.org

[commit-bot: I haz the power, 2016-12-08 17:15:17]

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-12-08 17:19:37]

CQ is committing da patch.

Bot data: {"patchset_id": 1, "attempt_start_ts": 1481217297634460, "parent_rev":
"4f87c65d659a8a0e3eaabfa1e140ba93f4f40ee3", "commit_rev":
"78821337bb8b808ead4b0df7ffbedba29d50d6e7"}

[commit-bot: I haz the power, 2016-12-08 17:20:03]

Description was changed from

==========
Explicitly make BrowserThread::SetDelegate specific to the IO thread.

The IO thread was already the only user and officially restricting users
of this API is required as BrowserThreadDelegates won't be compatible
with threads redirected to the TaskScheduler.

BUG=653916
==========

to

==========
Explicitly make BrowserThread::SetDelegate specific to the IO thread.

The IO thread was already the only user and officially restricting users
of this API is required as BrowserThreadDelegates won't be compatible
with threads redirected to the TaskScheduler.

BUG=653916
==========

[commit-bot: I haz the power, 2016-12-08 17:20:04]

Committed patchset #1 (id:1)

[commit-bot: I haz the power, 2016-12-08 17:22:58]

Description was changed from

==========
Explicitly make BrowserThread::SetDelegate specific to the IO thread.

The IO thread was already the only user and officially restricting users
of this API is required as BrowserThreadDelegates won't be compatible
with threads redirected to the TaskScheduler.

BUG=653916
==========

to

==========
Explicitly make BrowserThread::SetDelegate specific to the IO thread.

The IO thread was already the only user and officially restricting users
of this API is required as BrowserThreadDelegates won't be compatible
with threads redirected to the TaskScheduler.

BUG=653916

Committed: https://crrev.com/90becc91928a53cd44e37dde76e3f29a9507f271
Cr-Commit-Position: refs/heads/master@{#437271}
==========

[commit-bot: I haz the power, 2016-12-08 17:23:00]

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