-
Notifications
You must be signed in to change notification settings - Fork 296
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
Retry popen on 127 osx #306
Retry popen on 127 osx #306
Conversation
ff3b271
to
ccd77dc
Compare
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.
There are some clear (minor) changes needed, but I want someone else to take a look and see if we want to do this.
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.
nevermind; I am so annoyed that this is the best way to get a string representation of a thread ID.
I merged #305 since it seems obviously positive. I am less convinced about arbitrarily retrying: child processes are not guaranteed to be idempotent. If we want to implement a retry around "unzip" specifically on mac, I think that would be reasonable. It should not be implemented for all processes though. |
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.
See above comment.
ccd77dc
to
23535ef
Compare
…fails with code 127
a86c952
to
ecacaec
Compare
…ils with code 127" This reverts commit 23535ef.
Thanks, LGTM! |
Close microsoft/vcpkg#21905 bullet point 1.
Code 127 normally means
command not found
, but that does not really makes sense here. Sometimes (not often)unzip
returns 127 and sometimes not, when you retry it the return code is 0. I have no idea what the problem could be, but this implements a workaround by retrying the command once on mac when the return code is 127.