Why does this Task go directly from WaitingForActivation to RanToCompletion?

Asked Sep 27 '16 at 09:10

Active Sep 27 '16 at 09:10

Viewed 118 times

I'm running the following code in LINQPad:

void Main()
{
    Task x = TestAsync();

    do
    {
        Thread.Sleep(200);
        Console.WriteLine(x.Status);
    } while (x.Status != TaskStatus.RanToCompletion);
}

public async static Task TestAsync()
{
    await Task.Delay(1000);
    return;
}

The output is:

WaitingForActivation
WaitingForActivation
WaitingForActivation
WaitingForActivation
RanToCompletion

Why does it go directly from WaitingForActivation to RanToCompletion? Why is it apparently never in the Running state?

asked Sep 27 '16 at 09:10

Hydrargyrum

3,378
4
27
41

Note: I am deliberately not `await`ing the Task in this case. – Hydrargyrum Sep 27 '16 at 09:13
1

@Hydragyrum: Check out the [state machine diagrams](http://blog.stephencleary.com/2014/06/a-tour-of-task-part-3-status.html) on my blog. – Stephen Cleary Sep 27 '16 at 11:35

Why does this Task go directly from WaitingForActivation to RanToCompletion?

0 Answers0