Separate tests on Windows CI to Admin-Required and Non-Admin-Required - #2280

this looks like debug output - is it necessary?

No, that's how the parent process gets notification that the child process ended.

ok

art-UnelevatedProcess [](start = 18, length = 21)

it's too bad that runas doesn't give you any useful info about the running process

Indeed.
I was trying to find a way to avoid what I'm doing here.

break [](start = 24, length = 5)

are you relying on CI to bail if things take too long?

yeah. Should I include an explicit timeout logic?

possibly, i believe that appveyor has it's own time limitations on execution, it may be that nothing is needed here (or rather, any number you select will probably be wrong, up to the value that AppVeyor has)

Yeah, we control the timeout for all our project globally and it's currently 3 hours. I would leave it as is for now.

empty line above this why?

Artifacts from my experiments. Fixing.

This should be

if (-not $PSBoundParameters.ContainsKey('ExcludeTag'))

coreClrTestParams [](start = 81, length = 17)

don't you need to exclude RequiresAdmin tag for non admin?

Great catch!

Get-ExecutionPolicy -Scope LocalMachine | Should Be "ByPass" [](start = 12, length = 60)

I don't quite understand this:
attempt to set the localmachine policy, which is supposed to fail
then check the localmachine policy to see if it is what you just tried to set it to?
Shouldn't you get the localmachine policy in the BeforeAll, store it, then check against that value (rather than assume that ByPass will be correct)

Nope, that's how PowerShell works. The full error message text is:

Set-ExecutionPolicy : Windows PowerShell updated your execution policy successfully, but the setting is overridden by
a policy defined at a more specific scope.  Due to the override, your shell will retain its current effective
execution policy of RemoteSigned. Type "Get-ExecutionPolicy -List" to view your execution policy settings. For more
information please see "Get-Help Set-ExecutionPolicy".

FullyQualifiedErrorId : ExecutionPolicyOverride,Microsoft.PowerShell.Commands.SetExecutionPolicyCommand

Windows PowerShell updated your execution policy successfully, but the setting is overridden by
a policy defined at a more specific scope.

I'm going to add comments about it in the code, because it's indeed confusing

The guidance for FQEID validation is:

try {
    Set-ExecutionPolicy -Scope LocalMachine -ExecutionPolicy ByPass 
    throw "Expected exception: ExecutionPolicyOverride"
}
catch {
    $_.FullyQualifiedErrorId | Should Be 'ExecutionPolicyOverride,Microsoft.PowerShell.Commands.SetExecutionPolicyCommand' 

}

}

done

Add a comment here explaining why this is necessary.