Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Two System.Net.Sockets.Tests.SendPacketsAsync tests failing on Windows x64 debug #60267

Closed
radical opened this issue Oct 11, 2021 · 3 comments · Fixed by #63702
Closed

Two System.Net.Sockets.Tests.SendPacketsAsync tests failing on Windows x64 debug #60267

radical opened this issue Oct 11, 2021 · 3 comments · Fixed by #63702
Labels
area-System.Net.Sockets blocking-clean-ci Blocking PR or rolling runs of 'runtime' or 'runtime-extra-platforms' test-run-core Test failures in .NET Core test runs
Milestone

Comments

@radical
Copy link
Member

radical commented Oct 11, 2021

Build
Log

    System.Net.Sockets.Tests.SendPacketsAsync.SendPacketsElement_FileZeroCount_Success [FAIL]
      Timed out
      Expected: True
      Actual:   False
      Stack Trace:
        /_/src/libraries/System.Net.Sockets/tests/FunctionalTests/SendPacketsAsync.cs(700,0): at System.Net.Sockets.Tests.SendPacketsAsync.SendPackets(SendPacketsElement[] elements, SocketError expectedResult, Int32 bytesExpected, Byte[] contentExpected)
        /_/src/libraries/System.Net.Sockets/tests/FunctionalTests/SendPacketsAsync.cs(672,0): at System.Net.Sockets.Tests.SendPacketsAsync.SendPackets(SendPacketsElement element, Int32 bytesExpected, Byte[] contentExpected)
        /_/src/libraries/System.Net.Sockets/tests/FunctionalTests/SendPacketsAsync.cs(316,0): at System.Net.Sockets.Tests.SendPacketsAsync.SendPacketsElement_FileZeroCount_Success()
    System.Net.Sockets.Tests.SendPacketsAsync.SendPacketsElement_FileLargeOffset_Throws [FAIL]
      Timed out
      Expected: True
      Actual:   False
      Stack Trace:
        /_/src/libraries/System.Net.Sockets/tests/FunctionalTests/SendPacketsAsync.cs(700,0): at System.Net.Sockets.Tests.SendPacketsAsync.SendPackets(SendPacketsElement[] elements, SocketError expectedResult, Int32 bytesExpected, Byte[] contentExpected)
        /_/src/libraries/System.Net.Sockets/tests/FunctionalTests/SendPacketsAsync.cs(677,0): at System.Net.Sockets.Tests.SendPacketsAsync.SendPackets(SendPacketsElement element, SocketError expectedResult, Int32 bytesExpected)
        /_/src/libraries/System.Net.Sockets/tests/FunctionalTests/SendPacketsAsync.cs(341,0): at System.Net.Sockets.Tests.SendPacketsAsync.SendPacketsElement_FileLargeOffset_Throws()

Seen on #60258

@radical radical added the blocking-clean-ci Blocking PR or rolling runs of 'runtime' or 'runtime-extra-platforms' label Oct 11, 2021
@dotnet-issue-labeler dotnet-issue-labeler bot added area-System.Net.Sockets untriaged New issue has not been triaged by the area owner labels Oct 11, 2021
@ghost
Copy link

ghost commented Oct 11, 2021

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

Issue Details

Build
Log

    System.Net.Sockets.Tests.SendPacketsAsync.SendPacketsElement_FileZeroCount_Success [FAIL]
      Timed out
      Expected: True
      Actual:   False
      Stack Trace:
        /_/src/libraries/System.Net.Sockets/tests/FunctionalTests/SendPacketsAsync.cs(700,0): at System.Net.Sockets.Tests.SendPacketsAsync.SendPackets(SendPacketsElement[] elements, SocketError expectedResult, Int32 bytesExpected, Byte[] contentExpected)
        /_/src/libraries/System.Net.Sockets/tests/FunctionalTests/SendPacketsAsync.cs(672,0): at System.Net.Sockets.Tests.SendPacketsAsync.SendPackets(SendPacketsElement element, Int32 bytesExpected, Byte[] contentExpected)
        /_/src/libraries/System.Net.Sockets/tests/FunctionalTests/SendPacketsAsync.cs(316,0): at System.Net.Sockets.Tests.SendPacketsAsync.SendPacketsElement_FileZeroCount_Success()
    System.Net.Sockets.Tests.SendPacketsAsync.SendPacketsElement_FileLargeOffset_Throws [FAIL]
      Timed out
      Expected: True
      Actual:   False
      Stack Trace:
        /_/src/libraries/System.Net.Sockets/tests/FunctionalTests/SendPacketsAsync.cs(700,0): at System.Net.Sockets.Tests.SendPacketsAsync.SendPackets(SendPacketsElement[] elements, SocketError expectedResult, Int32 bytesExpected, Byte[] contentExpected)
        /_/src/libraries/System.Net.Sockets/tests/FunctionalTests/SendPacketsAsync.cs(677,0): at System.Net.Sockets.Tests.SendPacketsAsync.SendPackets(SendPacketsElement element, SocketError expectedResult, Int32 bytesExpected)
        /_/src/libraries/System.Net.Sockets/tests/FunctionalTests/SendPacketsAsync.cs(341,0): at System.Net.Sockets.Tests.SendPacketsAsync.SendPacketsElement_FileLargeOffset_Throws()

Seen on #60258

Author: radical
Assignees: -
Labels:

area-System.Net.Sockets, blocking-clean-ci, untriaged

Milestone: -

@krwq
Copy link
Member

krwq commented Nov 3, 2021

@karelz do you by any chance know if this is the same issue as #60017 ? the other one mention only one test case but this one seems to happen in pairs (i.e. happened as well in https://dev.azure.com/dnceng/public/_build/results?buildId=1448402&view=results)

@antonfirsov
Copy link
Member

@krwq this issue, #60017 and #58898 share the same root cause, impacting Win7 and Win11 CI machines only.

@ghost ghost added the in-pr There is an active PR which will close this issue when it is merged label Jan 12, 2022
@karelz karelz added this to the 7.0.0 milestone Jan 13, 2022
@karelz karelz removed the untriaged New issue has not been triaged by the area owner label Jan 13, 2022
@ghost ghost removed the in-pr There is an active PR which will close this issue when it is merged label Jan 15, 2022
@ghost ghost locked as resolved and limited conversation to collaborators Feb 14, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
area-System.Net.Sockets blocking-clean-ci Blocking PR or rolling runs of 'runtime' or 'runtime-extra-platforms' test-run-core Test failures in .NET Core test runs
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants