Skip to content

Conversation

@BruceForstall
Copy link
Contributor

The HelixCommandLines group must not call exit on the script or the HelixPostCommands and potentially other injected commands will not run.

Instead, figure out what the exit code should be, and set it properly (as ERRORLEVEL on Windows or $? on non-Windows).

Fixes #85621

The `HelixCommandLines` group must not call `exit` on the script
or the HelixPostCommands and potentially other injected commands
will not run.

Instead, figure out what the exit code should be, and set it properly
(as `ERRORLEVEL` on Windows or `$?` on non-Windows).

Fixes dotnet#85621
@ghost
Copy link

ghost commented May 2, 2023

Tagging subscribers to this area: @hoyosjs
See info in area-owners.md if you want to be subscribed.

Issue Details

The HelixCommandLines group must not call exit on the script or the HelixPostCommands and potentially other injected commands will not run.

Instead, figure out what the exit code should be, and set it properly (as ERRORLEVEL on Windows or $? on non-Windows).

Fixes #85621

Author: BruceForstall
Assignees: -
Labels:

area-Infrastructure-coreclr

Milestone: -

@BruceForstall
Copy link
Contributor Author

I verified that Linux, Windows, and Mac test runs all ran script lines after the XUnitLogChecker.

@BruceForstall BruceForstall merged commit a66af19 into dotnet:main May 2, 2023
@BruceForstall BruceForstall deleted the FixHelixCommandLineExitCode branch May 2, 2023 04:14
@ghost ghost locked as resolved and limited conversation to collaborators Jun 1, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

CI tests not running all commands

2 participants