Revert of New task queueing primitive for async tasks: TaskQueue.

Revert of New task queueing primitive for async tasks: TaskQueue. (patchset #5 id:80001 of https://codereview.webrtc.org/1919733002/ )

Reason for revert:
Reverting this temporarily while I figure out the issues with the Chrome on android GN debug build.

Original issue's description:
> New task queueing primitive for async tasks: TaskQueue.
> TaskQueue is a new way to asynchronously execute tasks sequentially
> in a thread safe manner with minimal locking.  The implementation
> uses OS supported APIs to do this that are compatible with async IO
> notifications from things like sockets and files.
>
> This class is a part of rtc_base_approved, so can be used by both
> the webrtc and libjingle parts of the WebRTC library.  Moving forward,
> we can replace rtc::Thread and webrtc::ProcessThread with this implementation.
>
> NOTE: It should not be assumed that all tasks that execute on a TaskQueue,
> run on the same thread.  E.g. on Mac and iOS, we use GCD dispatch queues
> which means that tasks might execute on different threads depending on
> what's the most efficient thing to do.

TBR=perkj@webrtc.org
# Skipping CQ checks because original CL landed less than 1 days ago.
NOPRESUBMIT=true
NOTREECHECKS=true
NOTRY=true

Committed: https://crrev.com/b296d0591cd71baacb4ecbd1a4698a6eb2b17bca
Cr-Commit-Position: refs/heads/master@{#12562}

[tommi, 2016-04-29 13:03:06]

Created Revert of New task queueing primitive for async tasks: TaskQueue.

[commit-bot: I haz the power, 2016-04-29 13:03:26]

CQ is trying da patch. Follow status at
 https://chromium-cq-status.appspot.com/patch-status/1935483002/1
View timeline at
 https://chromium-cq-status.appspot.com/patch-timeline/1935483002/1

[commit-bot: I haz the power, 2016-04-29 13:03:36]

Committed patchset #1 (id:1)

[tommi, 2016-04-29 20:28:00]

A revert of this CL (patchset #1 id:1) has been created in
https://codereview.webrtc.org/1927133004/ by tommi@webrtc.org.

The reason for reverting is: Relanding.

[commit-bot: I haz the power, 2016-05-01 22:01:54]

Description was changed from

==========
Revert of New task queueing primitive for async tasks: TaskQueue. (patchset #5
id:80001 of https://codereview.webrtc.org/1919733002/ )

Reason for revert:
Reverting this temporarily while I figure out the issues with the Chrome on
android GN debug build.

Original issue's description:
> New task queueing primitive for async tasks: TaskQueue.
> TaskQueue is a new way to asynchronously execute tasks sequentially
> in a thread safe manner with minimal locking.  The implementation
> uses OS supported APIs to do this that are compatible with async IO
> notifications from things like sockets and files.
> 
> This class is a part of rtc_base_approved, so can be used by both
> the webrtc and libjingle parts of the WebRTC library.  Moving forward,
> we can replace rtc::Thread and webrtc::ProcessThread with this implementation.
> 
> NOTE: It should not be assumed that all tasks that execute on a TaskQueue,
> run on the same thread.  E.g. on Mac and iOS, we use GCD dispatch queues
> which means that tasks might execute on different threads depending on
> what's the most efficient thing to do.

TBR=perkj@webrtc.org
# Skipping CQ checks because original CL landed less than 1 days ago.
NOPRESUBMIT=true
NOTREECHECKS=true
NOTRY=true
==========

to

==========
Revert of New task queueing primitive for async tasks: TaskQueue. (patchset #5
id:80001 of https://codereview.webrtc.org/1919733002/ )

Reason for revert:
Reverting this temporarily while I figure out the issues with the Chrome on
android GN debug build.

Original issue's description:
> New task queueing primitive for async tasks: TaskQueue.
> TaskQueue is a new way to asynchronously execute tasks sequentially
> in a thread safe manner with minimal locking.  The implementation
> uses OS supported APIs to do this that are compatible with async IO
> notifications from things like sockets and files.
>
> This class is a part of rtc_base_approved, so can be used by both
> the webrtc and libjingle parts of the WebRTC library.  Moving forward,
> we can replace rtc::Thread and webrtc::ProcessThread with this implementation.
>
> NOTE: It should not be assumed that all tasks that execute on a TaskQueue,
> run on the same thread.  E.g. on Mac and iOS, we use GCD dispatch queues
> which means that tasks might execute on different threads depending on
> what's the most efficient thing to do.

TBR=perkj@webrtc.org
# Skipping CQ checks because original CL landed less than 1 days ago.
NOPRESUBMIT=true
NOTREECHECKS=true
NOTRY=true

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

[commit-bot: I haz the power, 2016-05-01 22:01:55]

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