-
Notifications
You must be signed in to change notification settings - Fork 12.7k
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
Investigate making the buildbots network-access-free #35002
Comments
This is not only messing with PRs, it also killed the last three nightlies. |
I'd love to do this! I also have no idea how to do this easily though :( I have no idea why LLVM clones are timing out so much, I sent mail to GitHub but haven't gotten much of a response... |
You can clone and |
Buildbots are almost gone now, so closing. |
Still an issue with travis. |
Fundamentally I believe this is unfortunately just impossible for us. We will always be required to perform network requests on Travis/AppVeyor and I don't see an end in sight to that. That being said there are mitigation strategies for problems caused by this:
We've implemented a lot of this (mirroring on S3, retrying everything, etc), so I'm going to close this. Other general spurious network errors should be tracked at #40474 and we can investigate fixing those as they come up. |
Currently, the Rust buildbots (bors) all clone LLVM and other libs from Github. This seems to occasionally hang and cause mysterious spurious failures, possibly due to rate-limiting.
It could be better if we would do the
git submodule update
once and push the updated directory to the buildbots. We need to figure out how this interacts with lazy LLVM recompilation, but it should be possible.cc @rust-lang/tools
The text was updated successfully, but these errors were encountered: