-
Notifications
You must be signed in to change notification settings - Fork 1.6k
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
[WIP] download archive instead of cloning repo in integration tests #4703
Conversation
It works. |
@bors try |
download archive instead of cloning repo in integration tests changelog: none
Note that this PR will not lead to good win in build time. But it will not lead to |
☀️ Try build successful - checks-travis, status-appveyor |
The integration tests took ~20 minutes instead of the usual 10 minutes this time. Let's try again; maybe a caching issue? @bors try |
download archive instead of cloning repo in integration tests changelog: none
Yes, it is. Because of #4692 , the cache in try branch was not updated. |
☀️ Try build successful - checks-travis, status-appveyor |
I will investigate the regression in build time later. |
@@ -10,8 +10,9 @@ cargo install --force --debug --path . | |||
|
|||
echo "Running integration test for crate ${INTEGRATION}" | |||
|
|||
git clone --depth=1 "https://github.com/${INTEGRATION}.git" checkout |
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.
Couldn't this also be done with --single-branch
?
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.
Yes. But downloading tar.gz
archives is about 1 second faster than using git.
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.
So 1 second in a ~8 minute build? I think just using git
should be ok then?
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 would also rather keep it the current way if there is only a one-second speedup...
The aid is to check if clippy got much slower over the last few days. But not because of rust-lang#4703.
The aid is to check if clippy got much slower over the last few days. But not because of rust-lang#4703.
I would close this PR.
But none of them causes regressions in run-time like this PR. |
changelog: none