Revert of Use TaskScheduler instead of WorkerPool in v8_platform.cc.

Revert of Use TaskScheduler instead of WorkerPool in v8_platform.cc. (patchset #18 id:340001 of https://codereview.chromium.org/2610473002/ )

Reason for revert:
Causing extensions_unittests to hang and take 15 minutes.

BUG=694828
Original issue's description:
> Use TaskScheduler instead of WorkerPool in v8_platform.cc.
> 
> The following traits are used:
> 
> Priority: Inherited (default)
>   The priority is inherited from the calling context (i.e. TaskTraits
>   are initialized with the priority of the current task).
> 
> Shutdown behavior: CONTINUE_ON_SHUTDOWN
>   Tasks posted with this mode which have not started executing before
>   shutdown is initiated will never run. Tasks with this mode running at
>   shutdown will be ignored (the worker will not be joined).
> 
>   Note: Tasks that were previously posted to base::WorkerPool should
>   use this shutdown behavior because this is how base::WorkerPool
>   handles all its tasks.
> 
> MayBlock():
>   The task may block.
> 
> BUG=659191
> 
> Review-Url: https://codereview.chromium.org/2610473002
> Cr-Commit-Position: refs/heads/master@{#449976}
> Committed: https://chromium.googlesource.com/chromium/src/+/b83be4ca0e00b50b17619adf7f7de275455e9852

TBR=jochen@chromium.org,fdoray@chromium.org
# Not skipping CQ checks because original CL landed more than 1 days ago.
BUG=659191
Review-Url: https://codereview.chromium.org/2711703002
Cr-Commit-Position: refs/heads/master@{#452058}
Committed: https://chromium.googlesource.com/chromium/src/+/4df731b9954e2973ae8e206185f3de4556a806be

[jam, 2017-02-22 00:26:25]

The CQ bit was checked by jam@chromium.org

[jam, 2017-02-22 00:26:26]

Created Revert of Use TaskScheduler instead of WorkerPool in v8_platform.cc.

[commit-bot: I haz the power, 2017-02-22 00:27:39]

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, 2017-02-22 02:30:54]

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

[commit-bot: I haz the power, 2017-02-22 02:30:55]

Try jobs failed on following builders:
  cast_shell_linux on master.tryserver.chromium.linux (JOB_TIMED_OUT, no build
URL)
  chromeos_amd64-generic_chromium_compile_only_ng on
master.tryserver.chromium.linux (JOB_TIMED_OUT, no build URL)
  chromeos_daisy_chromium_compile_only_ng on master.tryserver.chromium.linux
(JOB_TIMED_OUT, no build URL)
  chromium_presubmit on master.tryserver.chromium.linux (JOB_TIMED_OUT, no build
URL)
  linux_chromium_asan_rel_ng on master.tryserver.chromium.linux (JOB_TIMED_OUT,
no build URL)
  linux_chromium_chromeos_ozone_rel_ng on master.tryserver.chromium.linux
(JOB_TIMED_OUT, no build URL)
  linux_chromium_chromeos_rel_ng on master.tryserver.chromium.linux
(JOB_TIMED_OUT, no build URL)
  linux_chromium_compile_dbg_ng on master.tryserver.chromium.linux
(JOB_TIMED_OUT, no build URL)
  linux_chromium_rel_ng on master.tryserver.chromium.linux (JOB_TIMED_OUT, no
build URL)
  linux_chromium_tsan_rel_ng on master.tryserver.chromium.linux (JOB_TIMED_OUT,
no build URL)

[jam, 2017-02-22 03:14:54]

The CQ bit was checked by jam@chromium.org

[commit-bot: I haz the power, 2017-02-22 03:15:43]

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

[jam, 2017-02-22 04:30:57]

The CQ bit was unchecked by jam@chromium.org

[jam, 2017-02-22 04:31:01]

The CQ bit was checked by jam@chromium.org

[commit-bot: I haz the power, 2017-02-22 04:31:03]

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

[jam, 2017-02-22 04:34:38]

The CQ bit was checked by jam@chromium.org

[commit-bot: I haz the power, 2017-02-22 04:35:43]

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, 2017-02-22 07:21:02]

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

[commit-bot: I haz the power, 2017-02-22 07:21:03]

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

[jam, 2017-02-22 14:43:42]

The CQ bit was checked by jam@chromium.org

[commit-bot: I haz the power, 2017-02-22 14:44:02]

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, 2017-02-22 15:25:02]

CQ is committing da patch.

Bot data: {"patchset_id": 240001, "attempt_start_ts": 1487774622860880,
"parent_rev": "2affa91c404bd93f81fdab4af5e6576abd64aeb2", "commit_rev":
"4df731b9954e2973ae8e206185f3de4556a806be"}

[commit-bot: I haz the power, 2017-02-22 15:25:39]

Description was changed from

==========
Revert of Use TaskScheduler instead of WorkerPool in v8_platform.cc. (patchset
#18 id:340001 of https://codereview.chromium.org/2610473002/ )

Reason for revert:
Causing extensions_unittests to hang and take 15 minutes.

BUG=694828

Original issue's description:
> Use TaskScheduler instead of WorkerPool in v8_platform.cc.
> 
> The following traits are used:
> 
> Priority: Inherited (default)
>   The priority is inherited from the calling context (i.e. TaskTraits
>   are initialized with the priority of the current task).
> 
> Shutdown behavior: CONTINUE_ON_SHUTDOWN
>   Tasks posted with this mode which have not started executing before
>   shutdown is initiated will never run. Tasks with this mode running at
>   shutdown will be ignored (the worker will not be joined).
> 
>   Note: Tasks that were previously posted to base::WorkerPool should
>   use this shutdown behavior because this is how base::WorkerPool
>   handles all its tasks.
> 
> MayBlock():
>   The task may block.
> 
> BUG=659191
> 
> Review-Url: https://codereview.chromium.org/2610473002
> Cr-Commit-Position: refs/heads/master@{#449976}
> Committed:
https://chromium.googlesource.com/chromium/src/+/b83be4ca0e00b50b17619adf7f7d...

TBR=jochen@chromium.org,fdoray@chromium.org
# Not skipping CQ checks because original CL landed more than 1 days ago.
BUG=659191
==========

to

==========
Revert of Use TaskScheduler instead of WorkerPool in v8_platform.cc. (patchset
#18 id:340001 of https://codereview.chromium.org/2610473002/ )

Reason for revert:
Causing extensions_unittests to hang and take 15 minutes.

BUG=694828

Original issue's description:
> Use TaskScheduler instead of WorkerPool in v8_platform.cc.
> 
> The following traits are used:
> 
> Priority: Inherited (default)
>   The priority is inherited from the calling context (i.e. TaskTraits
>   are initialized with the priority of the current task).
> 
> Shutdown behavior: CONTINUE_ON_SHUTDOWN
>   Tasks posted with this mode which have not started executing before
>   shutdown is initiated will never run. Tasks with this mode running at
>   shutdown will be ignored (the worker will not be joined).
> 
>   Note: Tasks that were previously posted to base::WorkerPool should
>   use this shutdown behavior because this is how base::WorkerPool
>   handles all its tasks.
> 
> MayBlock():
>   The task may block.
> 
> BUG=659191
> 
> Review-Url: https://codereview.chromium.org/2610473002
> Cr-Commit-Position: refs/heads/master@{#449976}
> Committed:
https://chromium.googlesource.com/chromium/src/+/b83be4ca0e00b50b17619adf7f7d...

TBR=jochen@chromium.org,fdoray@chromium.org
# Not skipping CQ checks because original CL landed more than 1 days ago.
BUG=659191

Review-Url: https://codereview.chromium.org/2711703002
Cr-Commit-Position: refs/heads/master@{#452058}
Committed:
https://chromium.googlesource.com/chromium/src/+/4df731b9954e2973ae8e206185f3...
==========

[commit-bot: I haz the power, 2017-02-22 15:25:41]

Committed patchset #2 (id:240001) as
https://chromium.googlesource.com/chromium/src/+/4df731b9954e2973ae8e206185f3...