Product: PowerShell Universal
Version: 3.4.4
On a default job, adding the following code to a standard job with an ErrorActionPreference of Continue leads to unexpected behavior
throw "Bad"
Write-Error "Hello"
Based on a powershell terminal, using throw 'Bad'; Write-Error 'Non-Term' and the same error action produces just “Bad” as an error. In PSU though it produces both outputs and marks the job as successful.
I believe this should be updated to work more inline with powershell native and terminating errors should be treated as failing the job