Skip to content

cargotest: Put output in build directory #32972

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

Merged
merged 1 commit into from
Apr 15, 2016
Merged

Conversation

alexcrichton
Copy link
Member

Right now cargotest uses TempDir to place output into the system temp
directory, but unfortunately this means that if the process is interrupted then
it'll leak the directory and that'll never get cleaned up. One of our bots
filled up its disk space and there were 20 cargotest directories lying around so
seems prudent to clean them up!

By putting the output in the build directory it should ensure that we don't leak
too many extra builds.

@rust-highfive
Copy link
Contributor

r? @aturon

(rust_highfive has picked a reviewer for you, use r? to override)

@alexcrichton
Copy link
Member Author

r? @brson

@rust-highfive rust-highfive assigned brson and unassigned aturon Apr 14, 2016
@brson
Copy link
Contributor

brson commented Apr 14, 2016

@bors r+ p=1

@bors
Copy link
Collaborator

bors commented Apr 14, 2016

📌 Commit 57014fd has been approved by brson

@bors
Copy link
Collaborator

bors commented Apr 15, 2016

⌛ Testing commit 57014fd with merge 3b35131...

@bors
Copy link
Collaborator

bors commented Apr 15, 2016

💔 Test failed - auto-win-msvc-64-cargotest

Right now cargotest uses `TempDir` to place output into the system temp
directory, but unfortunately this means that if the process is interrupted then
it'll leak the directory and that'll never get cleaned up. One of our bots
filled up its disk space and there were 20 cargotest directories lying around so
seems prudent to clean them up!

By putting the output in the build directory it should ensure that we don't leak
too many extra builds.
@alexcrichton
Copy link
Member Author

@bors: r=brson 73c2d2a

Chalking up another failure to Windows path limits

@bors
Copy link
Collaborator

bors commented Apr 15, 2016

⌛ Testing commit 73c2d2a with merge ccc7e95...

bors added a commit that referenced this pull request Apr 15, 2016
cargotest: Put output in build directory

Right now cargotest uses `TempDir` to place output into the system temp
directory, but unfortunately this means that if the process is interrupted then
it'll leak the directory and that'll never get cleaned up. One of our bots
filled up its disk space and there were 20 cargotest directories lying around so
seems prudent to clean them up!

By putting the output in the build directory it should ensure that we don't leak
too many extra builds.
@bors bors merged commit 73c2d2a into rust-lang:master Apr 15, 2016
@alexcrichton alexcrichton deleted the cargotest branch May 2, 2016 18:44
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants