Skip to content

Always fail if dotnet command failed #2535

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
May 2, 2025
Merged

Always fail if dotnet command failed #2535

merged 1 commit into from
May 2, 2025

Conversation

timcassell
Copy link
Collaborator

Fixes #2533

@timcassell timcassell added this to the v0.14.0 milestone Feb 29, 2024
@timcassell timcassell requested a review from adamsitnik March 6, 2024 04:19
@timcassell timcassell modified the milestones: v0.14.0, v0.15.x, v0.14.1 Aug 6, 2024
@timcassell
Copy link
Collaborator Author

@adamsitnik PTAL

@kg
Copy link
Member

kg commented Jan 6, 2025

The "the exit code might be 1 due to warnings" seems like something that might be worth keeping, maybe limit it to certain ranges of exit codes, or add some sort of command line switch like '--ignoreexitcode' so that people who were relying on the old behavior aren't stuck?

@timcassell
Copy link
Collaborator Author

timcassell commented Jan 6, 2025

I don't know the specifics around exit code 1 for warnings, but that file is quite old, so I'm thinking that may have only been an issue with early Core sdks (which we no longer support). I wasn't able to get that result with latest sdk.

@timcassell timcassell requested a review from AndreyAkinshin May 1, 2025 23:45
@timcassell timcassell merged commit 924ca6d into master May 2, 2025
@timcassell timcassell deleted the dotnet-fail branch May 2, 2025 20:51
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

MonoAOTLLVM run failed to build properly but still ran
3 participants