Skip to content
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

PowerShell exit code does not reset between packages in a single run #854

Closed
ferventcoder opened this issue Jul 8, 2016 · 0 comments
Closed

Comments

@ferventcoder
Copy link
Member

ferventcoder commented Jul 8, 2016

If a package has a non-zero exit code, the next package in the process will exit with that same code if it is set with a zero exit code. This was observed installing a package with dependencies and one of the dependencies failed but not the main package.

@ferventcoder ferventcoder added this to the 0.9.10.4 milestone Jul 8, 2016
@ferventcoder ferventcoder self-assigned this Jul 8, 2016
ferventcoder added a commit that referenced this issue Jul 24, 2016
There seems to be some bleed in package runs where the prior package
exit code is being applied to the next run. Ensure that the value is
reset each time.
ferventcoder added a commit that referenced this issue Jul 24, 2016
* stable:
  (maint) Skip log PowerShell resource assembly failures
  (GH-871) Fix - Uninstall zip: Path is empty string
  (maint) remove unused import
  (GH-854) Reset Exit Code between package runs
  (GH-852) Bump up the default log sizes
  (GH-867) NuGet.Core Errors Exit Code 1
  (GH-853) Handle null values better
  (GH-836) Fix - Use 32 bit 7zip
  (GH-847) Tab Completion Enhancements
  (GH-857) Fix - Sometimes paths contain null chars
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants