-
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
rustbuild: Clean out tmp directory on make clean
#34577
Conversation
r? @aturon (rust_highfive has picked a reviewer for you, use r? to override) |
rustbuild: Clean out tmp directory on `make clean` Right now we generate error index information into this directory, but it's never cleaned out. This means that if a build *bounces* because of something in this directory it'll continue to cause all future builds to fail because the relevant files are never removed.
⌛ Testing commit 98adb2f with merge 78812ca... |
💔 Test failed - auto-linux-64-opt-rustbuild |
Right now we generate error index information into this directory, but it's never cleaned out. This means that if a build *bounces* because of something in this directory it'll continue to cause all future builds to fail because the relevant files are never removed.
98adb2f
to
1e48a72
Compare
Ok the fact that both tmp/ and build/tmp/ exists is a bug that we need to fix... |
@bors: r=brson |
📌 Commit 1e48a72 has been approved by |
@bors: force |
💔 Test failed - auto-linux-cross-opt |
@bors: force |
⌛ Testing commit 1e48a72 with merge 2f7b87f... |
💔 Test failed - auto-linux-64-x-android-t |
@bors: retry On Thu, Jun 30, 2016 at 5:18 PM, bors notifications@github.com wrote:
|
rustbuild: Clean out tmp directory on `make clean` Right now we generate error index information into this directory, but it's never cleaned out. This means that if a build *bounces* because of something in this directory it'll continue to cause all future builds to fail because the relevant files are never removed.
Right now we generate error index information into this directory, but it's
never cleaned out. This means that if a build bounces because of something in
this directory it'll continue to cause all future builds to fail because the
relevant files are never removed.