-
Notifications
You must be signed in to change notification settings - Fork 5k
Disable some named synchronization object tests on Windows Server Core #113482
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
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Pull Request Overview
This PR updates the conditional test attributes to disable named synchronization object tests on Windows Server Core, in response to the observed behavior that Windows Server Core uses the same namespace for local and global objects.
- Updated conditional attributes in EventWaitHandleTests.cs, MutexTests.cs, and SemaphoreTests.cs to use PlatformDetection.IsNotWindowsNanoNorServerCore.
- Adjusted inline comments to reflect the inclusion of Server Core in the exclusion criteria.
Reviewed Changes
Copilot reviewed 3 out of 3 changed files in this pull request and generated no comments.
File | Description |
---|---|
src/libraries/System.Threading/tests/EventWaitHandleTests.cs | Updated conditional attribute and comment for Windows Server Core. |
src/libraries/System.Threading/tests/MutexTests.cs | Updated conditional attribute and comment for Windows Server Core. |
src/libraries/System.Threading/tests/SemaphoreTests.cs | Updated conditional attribute and comment for Windows Server Core. |
Tagging subscribers to this area: @mangod9 |
/azp run runtime-nativeaot-outerloop |
Azure Pipelines successfully started running 1 pipeline(s). |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thank you!
The new failing tests were added in #112213. It looks like Windows Server Core also does not use different namespaces for local and global named synchronization objects.