dotnet / runtime

.NET is a cross-platform runtime for cloud, mobile, desktop, and IoT apps.
https://docs.microsoft.com/dotnet/core/
MIT License
15.17k stars 4.72k forks source link

`System.IO.Pipes.Tests.NamedPipeTest_Specific.ClientConnectAsync_Cancel_With_InfiniteTimeout` failing on `Libraries Test Run release coreclr windows x86 Release` #69101

Open radical opened 2 years ago

radical commented 2 years ago

[Build(https://dev.azure.com/dnceng/public/_build/results?buildId=1761080&view=logs&jobId=ab70ab4f-0cf4-5814-7190-28e4ead6a7bf&j=ab70ab4f-0cf4-5814-7190-28e4ead6a7bf&t=7397d5bd-c86f-542b-6ad4-5cdbdcdf155e), and log.

    System.IO.Pipes.Tests.NamedPipeTest_Specific.ClientConnectAsync_Cancel_With_InfiniteTimeout [FAIL]
      System.TimeoutException : The operation has timed out.
      Stack Trace:
        /_/src/libraries/Common/tests/System/Threading/Tasks/TaskTimeoutExtensions.cs(0,0): at System.Threading.Tasks.TaskTimeoutExtensions.WaitAsync[TResult](Task`1 task, TimeSpan timeout, CancellationToken cancellationToken)
        /_/src/libraries/System.IO.Pipes/tests/NamedPipeTests/NamedPipeTest.Specific.cs(699,0): at System.IO.Pipes.Tests.NamedPipeTest_Specific.ClientConnectAsync_Cancel_With_InfiniteTimeout()
        --- End of stack trace from previous location ---

Test recently added in https://github.com/dotnet/runtime/pull/66877 . cc @cranberry-knight

{
  "ErrorMessage": "System.IO.Pipes.Tests.NamedPipeTest_Specific.ClientConnectAsync_Cancel_With_InfiniteTimeout [FAIL]",
  "BuildRetry": false
}

Report

Summary

24-Hour Hit Count 7-Day Hit Count 1-Month Count
0 0 0

Known issue validation

Build: :mag_right: Result validation: :warning: Validation could not be done without an Azure DevOps build URL on the issue. Please add it to the "Build: :mag_right:" line.

ghost commented 2 years ago

Tagging subscribers to this area: @dotnet/area-system-io See info in area-owners.md if you want to be subscribed.

Issue Details
[Build(https://dev.azure.com/dnceng/public/_build/results?buildId=1761080&view=logs&jobId=ab70ab4f-0cf4-5814-7190-28e4ead6a7bf&j=ab70ab4f-0cf4-5814-7190-28e4ead6a7bf&t=7397d5bd-c86f-542b-6ad4-5cdbdcdf155e), and [log](https://helixre8s23ayyeko0k025g8.blob.core.windows.net/dotnet-runtime-refs-pull-68921-merge-54ca1596f7314196b4/System.IO.Pipes.Tests/1/console.6ea66272.log?helixlogtype=result). ``` System.IO.Pipes.Tests.NamedPipeTest_Specific.ClientConnectAsync_Cancel_With_InfiniteTimeout [FAIL] System.TimeoutException : The operation has timed out. Stack Trace: /_/src/libraries/Common/tests/System/Threading/Tasks/TaskTimeoutExtensions.cs(0,0): at System.Threading.Tasks.TaskTimeoutExtensions.WaitAsync[TResult](Task`1 task, TimeSpan timeout, CancellationToken cancellationToken) /_/src/libraries/System.IO.Pipes/tests/NamedPipeTests/NamedPipeTest.Specific.cs(699,0): at System.IO.Pipes.Tests.NamedPipeTest_Specific.ClientConnectAsync_Cancel_With_InfiniteTimeout() --- End of stack trace from previous location --- ``` Test recently added in https://github.com/dotnet/runtime/pull/66877 . cc @cranberry-knight
Author: radical
Assignees: -
Labels: `area-System.IO`, `os-windows`
Milestone: -
stephentoub commented 1 year ago

@dotnet/area-system-io, please take a look / disable this test... it's failing many PRs.

jeffschwMSFT commented 7 months ago

removing blocking-clean-ci as this has not failed in 30 days

24-Hour Hit Count 7-Day Hit Count 1-Month Count
0 0 0