-
Notifications
You must be signed in to change notification settings - Fork 13.7k
Do not build LLVM tools for any of the tools #51725
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
Conversation
Nominating for beta as without this stable releases take ~3 hours which is much too long (other releases don't matter as much since they're manual). |
@bors r+ |
📌 Commit 2abeaea8b6ffbe7d134e7f4adf0310a2a4d54121 has been approved by |
The LLVM tool dependency was added by 54b0e07 for a single |
That code should be the one to depend on llvm tools, not compiletest or any other tool I think. If this fails CI I'll fix it otherwise doesn't seem important - probably the dependency edge already exists. |
⌛ Testing commit 2abeaea8b6ffbe7d134e7f4adf0310a2a4d54121 with merge 51228aeadfb7e2afae88d21cedac480e056f3a8d... |
💔 Test failed - status-appveyor |
Ok looks like |
None of the tools in the list should need LLVM tools themselves as far as I can tell; if this is incorrect, we can re-enable the tool building later. The primary reason for doing this is that rust-central-station uses the BuildManifest tool and building LLVM there is not cached: it takes ~1.5 hours on the 2 core machine. This commit should make nightlies and stable releases much faster.
@bors r=kennytm |
📌 Commit 557d05b has been approved by |
Do not build LLVM tools for any of the tools None of the tools in the list should need LLVM tools themselves as far as I can tell; if this is incorrect, we can re-enable the tool building later. The primary reason for doing this is that rust-central-station uses the BuildManifest tool and building LLVM there is not cached: it takes ~1.5 hours on the 2 core machine. This commit should make nightlies and stable releases much faster. Followup to #51459, r? @kennytm I'm mostly relying on CI to test this so probably don't roll it up; I'm not sure how to (and not particularly inclined to) wait for multiple hours to test this locally. I imagine that the failures should be fairly obvious when/if encountered.
☀️ Test successful - status-appveyor, status-travis |
[beta] Rollup backports Merged and approved: * #51725: Do not build LLVM tools for any of the tools * #51852: Don't use `ParamEnv::reveal_all()` if there is a real one available * #51686: yet another "old borrowck" bug around match default bindings * #51868: Remove process::id from 'Stabilized APIs' in 1.27.0 release notes * #51335: Prohibit `global_allocator` in submodules r? @ghost
None of the tools in the list should need LLVM tools themselves as far as I can
tell; if this is incorrect, we can re-enable the tool building later.
The primary reason for doing this is that rust-central-station uses the
BuildManifest tool and building LLVM there is not cached: it takes ~1.5
hours on the 2 core machine. This commit should make nightlies and
stable releases much faster.
Followup to #51459, r? @kennytm
I'm mostly relying on CI to test this so probably don't roll it up; I'm not sure how to (and not particularly inclined to) wait for multiple hours to test this locally. I imagine that the failures should be fairly obvious when/if encountered.