Skip to content

Test failure in System.Net.Http.Functional.Tests.SyncHttpHandler_HttpClientHandler_Cancellation_Test.GetAsync_CancelDuringResponseBodyReceived_Unbuffered_TaskCanceledQuickly #74122

Closed

Description

@carlossanlop

Hit the failure below in this RC1 PR: #74103

  • Libraries Test Run release coreclr Linux x64 Debug
  • Queues: (Centos.7.Amd64.Open)Ubuntu.1604.Amd64.Open@mcr.microsoft.com/dotnet-buildtools/prereqs:centos-7-mlnet-helix-20220601183719-dde38af+RedHat.7.Amd64.Open+(Debian.10.Amd64.Open)Ubuntu.1804.Amd64.Open@mcr.microsoft.com/dotnet-buildtools/prereqs:debian-10-helix-amd64-20220810215022-f344011+Ubuntu.1804.Amd64.Open

Callstack:

System.Net.Http.Functional.Tests.SyncHttpHandler_HttpClientHandler_Cancellation_Test.GetAsync_CancelDuringResponseBodyReceived_Unbuffered_TaskCanceledQuickly(chunkedTransfer: True, connectionClose: False, readOrCopyToAsync: False) [FAIL]
      System.TimeoutException : The operation has timed out.
      Stack Trace:
        /_/src/libraries/Common/tests/System/Net/Http/HttpClientHandlerTest.Cancellation.cs(260,0): at System.Net.Http.Functional.Tests.HttpClientHandler_Cancellation_Test.<>c__DisplayClass4_2.<<GetAsync_CancelDuringResponseBodyReceived_Unbuffered_TaskCanceledQuickly>b__0>d.MoveNext()
        --- End of stack trace from previous location ---
        /_/src/libraries/Common/tests/System/Net/Http/LoopbackServer.cs(101,0): at System.Net.Test.Common.LoopbackServer.CreateServerAsync(Func`2 funcAsync, Options options)
        /_/src/libraries/Common/tests/System/Net/Http/HttpClientHandlerTest.Cancellation.cs(228,0): at System.Net.Http.Functional.Tests.HttpClientHandler_Cancellation_Test.GetAsync_CancelDuringResponseBodyReceived_Unbuffered_TaskCanceledQuickly(Boolean chunkedTransfer, Boolean connectionClose, Boolean readOrCopyToAsync)

Activity

  1. ghost added
    untriagedNew issue has not been triaged by the area owner
    on Aug 18, 2022
  2. CarnaViire commented on Aug 18, 2022

    @CarnaViire
    Member

    Triage: we need to check how frequent this is. We might want to disable the test if it hurts CI. @rzikm could you have a look please?

  3. added this to the 7.0.0 milestone on Aug 18, 2022
  4. removed
    untriagedNew issue has not been triaged by the area owner
    on Aug 18, 2022
  5. carlossanlop commented on Aug 18, 2022

    @carlossanlop
    ContributorAuthor

    Thanks @CarnaViire . Also please decide if it needs a fix to get backported to RC1, if it meets the bar. If it's a test being disabled, you can backport that too to clean the other PRs CI results.

  6. rzikm commented on Aug 18, 2022

    @rzikm
    Member

    I have trouble finding this failure in Kusto

    cluster('engsrvprod.kusto.windows.net').database('engineeringdata').AzureDevOpsTests
        | where TestName contains 'GetAsync_CancelDuringResponseBodyReceived_Unbuffered_TaskCanceledQuickly'
        | where RunCompleted > ago(10d)

    returns empty result. Nor does looking for the specific JobId or WorkItemId find anything. @dotnet/dncenghot Can you take a look? It should find at least run from this: https://helixre107v0xdeko0k025g8.blob.core.windows.net/dotnet-runtime-refs-pull-74103-merge-e45453abd21e437ca1/System.Net.Http.Functional.Tests.Attempt.3/2/console.849c5012.log?helixlogtype=result

  7. missymessa commented on Aug 18, 2022

    @missymessa
    Member

    @rzikm I'm investigating the missing test in the test reporting tables.

  8. missymessa commented on Aug 18, 2022

    @missymessa
    Member

    @rzikm it looks like these work items ran during the storage outage we had a couple days ago and since we rely on uploading test data to our storage account to ingest into Kusto, this disrupted the process. I'm sorry that you're not able to find the data you want for that test.

  9. ChadNedzlek commented on Aug 18, 2022

    @ChadNedzlek
    Contributor

    If you look at that PR, this failure is present: System.Net.Http.Functional.Tests Work Item

    Meaning we didn't run the functional tests at all (or, at least, didn't report them).

  10. MattGal commented on Aug 18, 2022

    @MattGal
    Member

    If you look at that PR, this failure is present: System.Net.Http.Functional.Tests Work Item

    Meaning we didn't run the functional tests at all (or, at least, didn't report them).

    This run was definitely impacted by dotnet/arcade#10358. I've given them 100 more examples of the problem and notified the issue. You can follow along via the IcM ticket linked.

  11. wfurt commented on Aug 22, 2022

    @wfurt
    Member

    I run the query again and I only see 4 failures on 8/19 (all RedHat7) no failure afterwards and no failure on main.
    This does not look like regression to me @karelz. The test is time sensitive and verifies Cancellation that is best-effort.

    My suggestion would be to move to 8 and add more diagnostic and perhaps change

    to PassingTestTimeout

  12. karelz commented on Aug 23, 2022

    @karelz
    Member

    Triage: Looks like it was one time hiccup. There does not seem to be more failures. Moving to 8.0.

  13. modified the milestones: 7.0.0, 8.0.0 on Aug 23, 2022
  14. self-assigned this
    on Aug 23, 2022
  15. wfurt commented on Jun 7, 2023

    @wfurt
    Member

    can you please check failure rate @rzikm? It seems like we did not see recent failures and RedHat7 is no longer supported AFAIK. We should probably close it unless there is evidence this is still failing regularly.

  16. assigned and unassigned on Jun 7, 2023
  17. rzikm commented on Jul 20, 2023

    @rzikm
    Member

    No recent hard failures, only PassedOnRerun, closing now as no action is necessary for time being and RH7 is no longer supported.

  18. removed their assignment
    on Jul 20, 2023
  19. ghost locked as resolved and limited conversation to collaborators on Aug 19, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

      Milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions