std.Build.Step: make result returning correctly with evalZigProcess #19922
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Atomk
reviewed
May 10, 2024
RossComputerGuy
force-pushed
the
fix/expected-error-build
branch
from
d7b212f
to
f4d9336
Compare
Fixes ziglang#18941 by moving the "checkCompileErrors" call from Build.Step.Compile to Build.Step and returning result if the errors match as expected.
RossComputerGuy
force-pushed
the
fix/expected-error-build
branch
from
f4d9336
to
32d5425
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Fixes #18941 by moving the
checkCompileErrorscall fromBuild.Step.CompiletoBuild.Stepand returning result if the errors match as expected.Continued from #18943