-
Notifications
You must be signed in to change notification settings - Fork 4.8k
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
Multicast Socket tests failing on Nano #26286
Labels
area-System.Net.Sockets
disabled-test
The test is disabled in source code against the issue
os-windows-nano
Nano Windows SKU
Milestone
Comments
davidsh
referenced
this issue
in dotnet/corefx
May 25, 2018
maryamariyan
referenced
this issue
in maryamariyan/corefx
May 30, 2018
See: #29929 Conflicts: src/System.Net.Sockets/tests/FunctionalTests/SocketOptionNameTest.cs
danmoseley
referenced
this issue
in dotnet/corefx
May 31, 2018
* Disable SafeServiceControllerTests.GetServices test (#29924) https://github.com/dotnet/corefx/issues/19223 * Disable serial ports tests on Windows Nano (#29793) Fix #29756 * Merge pull request #29789 from stephentoub/nanotests Disable some tests on Nano server * Disable multicast socket tests on Nano (#29931) See: #29929 Conflicts: src/System.Net.Sockets/tests/FunctionalTests/SocketOptionNameTest.cs * Disable System.DirectoryServices ActiveDirectory tests on Nano Server (#29857) * Replaces ConditionalClass with ConditionalFact or ConditionalTheory
davidsh
referenced
this issue
in davidsh/corefx
Apr 14, 2019
One of the oldest issues #4887 was about the Windows socket option, ReuseUnicastPort. This test was disabled several years ago because it was very difficult to test in CI since it required not only a newer version of Windows but also specific network settings on the machine. At this point, there is not any way to reliably test this. And the end-to-end test isn't really of high value for .NET Core since we would really be mostly testing an OS feature. As part of cleaning that issue up, I cleaned up the rest of the tests, some of which were marked as Outerloop but didn't need to be. Closes #29929 Closes #21327 Closes #4887
stephentoub
referenced
this issue
in dotnet/corefx
Apr 15, 2019
One of the oldest issues #4887 was about the Windows socket option, ReuseUnicastPort. This test was disabled several years ago because it was very difficult to test in CI since it required not only a newer version of Windows but also specific network settings on the machine. At this point, there is not any way to reliably test this. And the end-to-end test isn't really of high value for .NET Core since we would really be mostly testing an OS feature. As part of cleaning that issue up, I cleaned up the rest of the tests, some of which were marked as Outerloop but didn't need to be. Closes #29929 Closes #21327 Closes #4887
ghost
locked as resolved and limited conversation to collaborators
Dec 16, 2020
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Labels
area-System.Net.Sockets
disabled-test
The test is disabled in source code against the issue
os-windows-nano
Nano Windows SKU
dotnet/corefx#29903 (comment)
The Sockets multicast tests are failing on Nano:
https://mc.dot.net/#/user/davidsh/pr~2Fjenkins~2Fdotnet~2Fcorefx~2Fmaster~2F/test~2Ffunctional~2Fcli~2F/5f5dae7b004d88bdc2927927d655380c56087396/workItem/System.Net.Sockets.Tests
The text was updated successfully, but these errors were encountered: