Remove call to IsRunningSequenceOnCurrentThread() from api_resource_manager.h.

Remove call to IsRunningSequenceOnCurrentThread() from api_resource_manager.h.

SequencedWorkerPool is being migrated to base/task_scheduler and there
is no equivalent to IsRunningSequenceOnCurrentThread() in
base/task_scheduler.

We believe that always doing work asynchronously is cleaner than using
this pattern:

if (pool->IsRunningSequencedOnCurrentThread(token))
 DoSequencedWork();
else
 pool->PostSequencedWorkerTask(token, FROM_HERE, Bind(&DoSequencedWork));

Developers should us SequenceChecker to verify that tasks run
sequentially. Unlike
SequencedWorkerPool::IsRunningSequenceOnCurrentThread(),
SequenceChecker works everywhere in Chrome (MessageLoop,
SequencedWorkerPool, base/task_scheduler...).

BUG=622400
Committed: https://crrev.com/62f47315fa2bae98943888334e2787ce308659e8
Cr-Commit-Position: refs/heads/master@{#416679}

[fdoray, 2016-09-02 20:11:39]

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

[commit-bot: I haz the power, 2016-09-02 20:12:05]

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-09-02 21:08:37]

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

[commit-bot: I haz the power, 2016-09-02 21:08:37]

Dry run: This issue passed the CQ dry run.

[fdoray, 2016-09-06 14:03:29]

fdoray@chromium.org changed reviewers:
+ reillyg@chromium.org

[fdoray, 2016-09-06 14:03:30]

PTAL

[Reilly Grant (use Gerrit), 2016-09-06 17:35:05]

lgtm

[fdoray, 2016-09-06 17:44:58]

The CQ bit was checked by fdoray@chromium.org

[commit-bot: I haz the power, 2016-09-06 17:45:46]

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-09-06 18:37:18]

Committed patchset #1 (id:1)

[commit-bot: I haz the power, 2016-09-06 18:39:40]

Description was changed from

==========
Remove call to IsRunningSequenceOnCurrentThread() from api_resource_manager.h.

SequencedWorkerPool is being migrated to base/task_scheduler and there
is no equivalent to IsRunningSequenceOnCurrentThread() in
base/task_scheduler.

We believe that always doing work asynchronously is cleaner than using
this pattern:

if (pool->IsRunningSequencedOnCurrentThread(token))
 DoSequencedWork();
else
 pool->PostSequencedWorkerTask(token, FROM_HERE, Bind(&DoSequencedWork));

Developers should us SequenceChecker to verify that tasks run
sequentially. Unlike
SequencedWorkerPool::IsRunningSequenceOnCurrentThread(),
SequenceChecker works everywhere in Chrome (MessageLoop,
SequencedWorkerPool, base/task_scheduler...).

BUG=622400
==========

to

==========
Remove call to IsRunningSequenceOnCurrentThread() from api_resource_manager.h.

SequencedWorkerPool is being migrated to base/task_scheduler and there
is no equivalent to IsRunningSequenceOnCurrentThread() in
base/task_scheduler.

We believe that always doing work asynchronously is cleaner than using
this pattern:

if (pool->IsRunningSequencedOnCurrentThread(token))
 DoSequencedWork();
else
 pool->PostSequencedWorkerTask(token, FROM_HERE, Bind(&DoSequencedWork));

Developers should us SequenceChecker to verify that tasks run
sequentially. Unlike
SequencedWorkerPool::IsRunningSequenceOnCurrentThread(),
SequenceChecker works everywhere in Chrome (MessageLoop,
SequencedWorkerPool, base/task_scheduler...).

BUG=622400

Committed: https://crrev.com/62f47315fa2bae98943888334e2787ce308659e8
Cr-Commit-Position: refs/heads/master@{#416679}
==========

[commit-bot: I haz the power, 2016-09-06 18:39:41]

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