-
Notifications
You must be signed in to change notification settings - Fork 10.6k
utils: Make update-checkout run in parallel. #5048
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
Conversation
|
@swift-ci Please test |
|
Build failed |
80948b7 to
e37afd8
Compare
|
@swift-ci Please test |
|
Build failed |
|
Build failed |
|
@swift-ci Please test |
|
Build failed |
|
Build failed |
95a9eb3 to
8f23631
Compare
|
|
||
| def update_single_repository(repo_path, branch, reset_to_remote, should_clean, | ||
| cross_repo): | ||
| def update_single_repository(args): |
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.
Shouldn't it be *args?
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.
Pool.map_async has to call update_single_repository with the fixed five arguments. I unpack them on the second line, maybe that's not as pythonic as it could be? args could be a tuple instead of a list as well.
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.
That is correct, but you can no longer call update_single_repository supplying just those 5 arguments, you'd have to wrap them in either tuple or a list. I just pointed it out as it might cause problems.
|
@swift-ci Please test |
1 similar comment
|
@swift-ci Please test |
|
I'm a little concerned about this because when I run it over ssh every remote command prompts me for my key password. |
|
@jrose-apple Well that would stop me from pushing it for sure. I wonder why it's doing that. |
|
Sorry, I mean the current one does that. My understanding is that the SSH key server just isn't accessible during an ssh session, or maybe that the key server is associated with a user session and I haven't started one for my ssh session. I suppose that's something I could poke into separately. |
8f23631 to
c02faa9
Compare
|
@swift-ci Please test |
|
Build failed |
|
@swift-ci Please test |
|
Build failed |
|
Build failed |
|
@swift-ci Please test |
|
Build failed |
|
Build failed |
|
@swift-ci Please test |
|
Build failed |
|
Build failed |
|
These failures were fixed in #5187. What's going on here? |
|
Looks like the merge conflict didn't short-circuit the build. Mishal is looking into it. |
8f23631 to
0ccc8ae
Compare
|
@swift-ci Please smoke test |
0ccc8ae to
46fdc7a
Compare
|
@swift-ci Please smoke test |
46fdc7a to
1985972
Compare
|
@swift-ci Please clean test |
|
Build failed |
|
@swift-ci Please clean smoke test |
|
Build failed |
f44cbac to
3753f59
Compare
|
@swift-ci Please clean smoke test |
WIP