[content]: Don't use task's from_here when posting delayed EnqueueTask on Task Queue Manager.

[content]: Don't use task's from_here when posting delayed EnqueueTask on Task Queue Manager.

When posting a delayed task in the task queue manager we post a wrapping task
which enqueues the actual task on the underlying message loop. It is confusing
to have this task use the actual task's from_here since it looks like the task
get's run at this point, which is not the case.

Committed: https://crrev.com/2794174de0ad4ee60b0a47408ec56c3de6cb2f07
Cr-Commit-Position: refs/heads/master@{#318052}

[rmcilroy, 2015-02-25 13:54:10]

rmcilroy@chromium.org changed reviewers:
+ skyostil@chromium.org

[rmcilroy, 2015-02-25 13:54:11]

Found this while trying to verify the long idle stuff works - it's a bit
confusing to the task's from_here info appear twice.  PTAL, thanks.

[Sami, 2015-02-25 14:08:19]

On 2015/02/25 13:54:11, rmcilroy wrote:
> Found this while trying to verify the long idle stuff works - it's a bit
> confusing to the task's from_here info appear twice.  PTAL, thanks.

Well spotted. We can still see where the task originally came from where it gets
to run. lgtm.

I think this is the patch with the shortest vi equivalent I've seen so far: 9~
:)

[rmcilroy, 2015-02-25 14:19:09]

On 2015/02/25 14:08:19, Sami wrote:
> On 2015/02/25 13:54:11, rmcilroy wrote:
> > Found this while trying to verify the long idle stuff works - it's a bit
> > confusing to the task's from_here info appear twice.  PTAL, thanks.
> 
> Well spotted. We can still see where the task originally came from where it
gets
> to run. lgtm.
> 
> I think this is the patch with the shortest vi equivalent I've seen so far: 9~
> :)

Achievement unlocked ;).

I also made the same change to SingleThreadIdleTaskRunner for the same reason,
so now 9~ x2.  Still OK?

[Sami, 2015-02-25 14:25:21]

On 2015/02/25 14:19:09, rmcilroy wrote:
> On 2015/02/25 14:08:19, Sami wrote:
> > On 2015/02/25 13:54:11, rmcilroy wrote:
> > > Found this while trying to verify the long idle stuff works - it's a bit
> > > confusing to the task's from_here info appear twice.  PTAL, thanks.
> > 
> > Well spotted. We can still see where the task originally came from where it
> gets
> > to run. lgtm.
> > 
> > I think this is the patch with the shortest vi equivalent I've seen so far:
9~
> > :)
> 
> Achievement unlocked ;).
> 
> I also made the same change to SingleThreadIdleTaskRunner for the same reason,
> so now 9~ x2.  Still OK?

Still lgtm.

[rmcilroy, 2015-02-25 14:26:21]

The CQ bit was checked by rmcilroy@chromium.org

[commit-bot: I haz the power, 2015-02-25 14:26:44]

CQ is trying da patch. Follow status at
 https://chromium-cq-status.appspot.com/patch-status/959713002/20001

[commit-bot: I haz the power, 2015-02-25 14:43:15]

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

[commit-bot: I haz the power, 2015-02-25 14:43:16]

Try jobs failed on following builders:
  mac_chromium_rel_ng on tryserver.chromium.mac (JOB_FAILED,
http://build.chromium.org/p/tryserver.chromium.mac/builders/mac_chromium_rel_...)

[rmcilroy, 2015-02-25 15:05:58]

The CQ bit was checked by rmcilroy@chromium.org

[commit-bot: I haz the power, 2015-02-25 15:06:29]

CQ is trying da patch. Follow status at
 https://chromium-cq-status.appspot.com/patch-status/959713002/20001

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

Committed patchset #2 (id:20001)

[commit-bot: I haz the power, 2015-02-25 15:42:18]

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