Passed cancellationToken might be default.

[ManickaP]

In cases like WinHttpHandler (which is also build against .NET Framework), there is no way how to properly pass cancellationToken to content's CopyToAsync. The overloads accepting it are recent addition and not part of .NET Standard.
The tests were deadlocking waiting for cts.Task which is supposed to be finished from cancellationToken.Register(...) on the token that is not bound to test's TaskCompletionSource.

Fixes #36689

cc: @stephentoub

[ghost]

Tagging subscribers to this area: @dotnet/ncl
Notify danmosemsft if you want to be subscribed.

[ManickaP]

/azp run runtime-libraries outerloop

[azure-pipelines]

Azure Pipelines successfully started running 1 pipeline(s).

[ManickaP]

BTW, does the test still make sense if we're bypassing the passed in cancellationToken?

[stephentoub]

BTW, does the test still make sense if we're bypassing the passed in cancellationToken?

The test is named "PostAsync_Cancel_CancellationTokenPassedToContent"... if the cancellation token isn't passed to the content with WinHttpHandler, then we probably should just skip the test on WinHttpHandler ;)

[ManickaP]

/azp run runtime-libraries outerloop

[azure-pipelines]

Azure Pipelines successfully started running 1 pipeline(s).

[ManickaP]

Test skipped on WinHttpHandler completely.