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

Revert of Use TaskScheduler instead of WorkerPool in gbm_surfaceless.cc. (patchset #2 id:20001 of https://codereview.chromium.org/2609733002/ )

Reason for revert:
Causes the UI to crash on peach_pit and multiple HWTest failures on the PFQ and the informational builder. See BUG=678296
.

Original issue's description:
> Use TaskScheduler instead of WorkerPool in gbm_surfaceless.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.
>
> May Block:
>   Tasks posted with MayBlock() may block. This includes but is not
>   limited to tasks that wait on synchronous file I/O operations:
>   read or write a file from disk, interact with a pipe or a socket,
>   rename or delete a file, enumerate files in a directory, etc. This
>   trait isn't required for the mere use of locks.
>
> BUG=659191
>
> Committed: https://crrev.com/0127fd25bd985f1f5f87c0a7c060d3159142086a
> Cr-Commit-Position: refs/heads/master@{#441139}

TBR=dnicoara@chromium.org,fdoray@chromium.org
# Not skipping CQ checks because original CL landed more than 1 days ago.
BUG=659191
Committed: https://crrev.com/2b42f8092f30184dda0b785d26fdf7538c394220
Cr-Commit-Position: refs/heads/master@{#441438}

[afakhry, 2017-01-04 19:23:09]

The CQ bit was checked by afakhry@chromium.org

[afakhry, 2017-01-04 19:23:09]

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

[commit-bot: I haz the power, 2017-01-04 19:23:37]

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-01-04 20:00:45]

CQ is committing da patch.

Bot data: {"patchset_id": 1, "attempt_start_ts": 1483557789241110, "parent_rev":
"689de0633e3cdb19768688e7afb6f1caa3f16357", "commit_rev":
"a56b7b4a76f090f85dbffefaa7ceabc8e2c017ee"}

[commit-bot: I haz the power, 2017-01-04 20:01:17]

Description was changed from

==========
Revert of Use TaskScheduler instead of WorkerPool in gbm_surfaceless.cc.
(patchset #2 id:20001 of https://codereview.chromium.org/2609733002/ )

Reason for revert:
Causes the UI to crash on peach_pit and multiple HWTest failures on the PFQ and
the informational builder. See BUG=678296.

Original issue's description:
> Use TaskScheduler instead of WorkerPool in gbm_surfaceless.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.
> 
> May Block:
>   Tasks posted with MayBlock() may block. This includes but is not
>   limited to tasks that wait on synchronous file I/O operations:
>   read or write a file from disk, interact with a pipe or a socket,
>   rename or delete a file, enumerate files in a directory, etc. This
>   trait isn't required for the mere use of locks.
> 
> BUG=659191
> 
> Committed: https://crrev.com/0127fd25bd985f1f5f87c0a7c060d3159142086a
> Cr-Commit-Position: refs/heads/master@{#441139}

TBR=dnicoara@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 gbm_surfaceless.cc.
(patchset #2 id:20001 of https://codereview.chromium.org/2609733002/ )

Reason for revert:
Causes the UI to crash on peach_pit and multiple HWTest failures on the PFQ and
the informational builder. See BUG=678296.

Original issue's description:
> Use TaskScheduler instead of WorkerPool in gbm_surfaceless.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.
> 
> May Block:
>   Tasks posted with MayBlock() may block. This includes but is not
>   limited to tasks that wait on synchronous file I/O operations:
>   read or write a file from disk, interact with a pipe or a socket,
>   rename or delete a file, enumerate files in a directory, etc. This
>   trait isn't required for the mere use of locks.
> 
> BUG=659191
> 
> Committed: https://crrev.com/0127fd25bd985f1f5f87c0a7c060d3159142086a
> Cr-Commit-Position: refs/heads/master@{#441139}

TBR=dnicoara@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/2612853002
==========

[commit-bot: I haz the power, 2017-01-04 20:01:18]

Committed patchset #1 (id:1)

[commit-bot: I haz the power, 2017-01-04 20:03:23]

Description was changed from

==========
Revert of Use TaskScheduler instead of WorkerPool in gbm_surfaceless.cc.
(patchset #2 id:20001 of https://codereview.chromium.org/2609733002/ )

Reason for revert:
Causes the UI to crash on peach_pit and multiple HWTest failures on the PFQ and
the informational builder. See BUG=678296.

Original issue's description:
> Use TaskScheduler instead of WorkerPool in gbm_surfaceless.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.
> 
> May Block:
>   Tasks posted with MayBlock() may block. This includes but is not
>   limited to tasks that wait on synchronous file I/O operations:
>   read or write a file from disk, interact with a pipe or a socket,
>   rename or delete a file, enumerate files in a directory, etc. This
>   trait isn't required for the mere use of locks.
> 
> BUG=659191
> 
> Committed: https://crrev.com/0127fd25bd985f1f5f87c0a7c060d3159142086a
> Cr-Commit-Position: refs/heads/master@{#441139}

TBR=dnicoara@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/2612853002
==========

to

==========
Revert of Use TaskScheduler instead of WorkerPool in gbm_surfaceless.cc.
(patchset #2 id:20001 of https://codereview.chromium.org/2609733002/ )

Reason for revert:
Causes the UI to crash on peach_pit and multiple HWTest failures on the PFQ and
the informational builder. See BUG=678296.

Original issue's description:
> Use TaskScheduler instead of WorkerPool in gbm_surfaceless.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.
>
> May Block:
>   Tasks posted with MayBlock() may block. This includes but is not
>   limited to tasks that wait on synchronous file I/O operations:
>   read or write a file from disk, interact with a pipe or a socket,
>   rename or delete a file, enumerate files in a directory, etc. This
>   trait isn't required for the mere use of locks.
>
> BUG=659191
>
> Committed: https://crrev.com/0127fd25bd985f1f5f87c0a7c060d3159142086a
> Cr-Commit-Position: refs/heads/master@{#441139}

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

Committed: https://crrev.com/2b42f8092f30184dda0b785d26fdf7538c394220
Cr-Commit-Position: refs/heads/master@{#441438}
==========

[commit-bot: I haz the power, 2017-01-04 20:03:24]

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