make TestUserCredentialsPropertiesOnWindows stable on Windows Server Core#47031
make TestUserCredentialsPropertiesOnWindows stable on Windows Server Core#47031danmoseley merged 3 commits intodotnet:masterfrom
Conversation
this is to try to make TestUserCredentialsPropertiesOnWindows stable on Windows Server Core
adamsitnik
added
area-System.Diagnostics.Process
test-bug
|
Tagging subscribers to this area: @eiriktsarpalis Issue Details
|
|
/azp run runtime-libraries-coreclr outerloop-windows |
|
Azure Pipelines successfully started running 1 pipeline(s). |
…rent exception (throw in the catch block)?
|
/azp run runtime-libraries-coreclr outerloop-windows |
|
Azure Pipelines successfully started running 1 pipeline(s). |
What if we don't give the user rigts to execute it at all?
|
/azp run runtime-libraries-coreclr outerloop-windows |
|
Azure Pipelines successfully started running 1 pipeline(s). |
|
@eiriktsarpalis it's now properly passing |
|
|
||
| // ensure the new user can access the .exe (otherwise you get Access is denied exception) | ||
| SetAccessControl(username, p.StartInfo.FileName, add: true); | ||
| if (PlatformDetection.IsNotWindowsServerCore) // for this particular Windows version it fails with Attempted to perform an unauthorized operation (#46619) |
There was a problem hiding this comment.
The test is still valid without this? If the test succeeds without this on Windows Server Core, why is it needed on other Windows?
There was a problem hiding this comment.
I've added this recently when I was working on re-enabling this test and it was mandatory on my machine to make it work (#46083)
I have no idea why it does not work on machines from this certain pool. Is it a thing related to Windows Server? Some custom helix machine setup?
The test is restricted to admin accounts only:
Which makes it even more confusing (I would assume that Admin accounts which can create other user accounts can also add permissions to files?)
danmoseley
left a comment
danmoseley
left a comment
There was a problem hiding this comment.
I would like to know the answer too, but merging this gets us into a better state.
|
Hit this again -- so I'm merging! |
|
unrelated failures. |
ghost
locked as resolved and limited conversation to collaborators
3 participants
Fixes #46619