-
Notifications
You must be signed in to change notification settings - Fork 1.4k
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
Fixed /restore and /graph conjunction error on exit code #9461
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
nit: I think it would be slightly better if the success =
assignments were done right after the respective results are calculated. The current code effectively repeats the condition graphResult != null && !saveProjectResult
in two places in an non-obvious way and it would be easy to have them diverge and introduce a similar bug in the future. Especially given what a monster of a method this is.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I like the refactoring a lot!
I think we should target vs17.9 branch for this PR, since this is a bug? |
Fixes #9443
Context
When the
/graph
and/restore
are used within the same command, the build exit code will always be 0. This is because of the variable used to define success of the restore action overrides the success of the graph build.Changes Made
Added an extra condition when defining the success of the build to account for this case.
Testing
Made sure existing tests passed and added a unit test for this case, an some manual testing.