You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Do not assume windows_build_command is a single line (#154)
`windows_build_command` was prefixed with a `Invoke-Program` to ensure
we catch errors, but this then misses multiline commands. Move
`Invoke-Program` up into the default command and then assume that it is
passed if a non-default command is used.
Note that `$ErrorActionPreference = 'Stop'` is not an option here - it
only stops for cmdlets, not native commands.
`$PSNativeCommandUseErrorActionPreference = $true` allows stopping on
native commands too, but that was only introduced in PowerShell 7.3.
windowsservercore-ltsc2022 has 5.1 by default (though we could install a
newer if we wanted to).
Update PR testing in this repo to use `Invoke-Program` to then actually
catch failures.
Copy file name to clipboardExpand all lines: .github/workflows/swift_package_test.yml
+2-2Lines changed: 2 additions & 2 deletions
Original file line number
Diff line number
Diff line change
@@ -102,7 +102,7 @@ on:
102
102
Windows Command Prompt command to build and test the package.
103
103
Note that Powershell does not automatically exit if a subcommand fails. The Invoke-Program utility is available to propagate non-zero exit codes.
104
104
It is strongly encouraged to run all command using `Invoke-Program` unless you want to continue on error eg. `Invoke-Program git apply patch.diff` instead of `git apply patch.diff`.
105
-
default: "swift test"
105
+
default: "Invoke-Program swift test"
106
106
macos_env_vars:
107
107
description: "Newline separated list of environment variables"
0 commit comments