Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Spurious "no space left on device" exceptions #40359

Closed
alexcrichton opened this issue Mar 8, 2017 · 7 comments · Fixed by #40382
Closed

Spurious "no space left on device" exceptions #40359

alexcrichton opened this issue Mar 8, 2017 · 7 comments · Fixed by #40382
Labels
A-spurious Area: Spurious failures in builds (spuriously == for no apparent reason)

Comments

@alexcrichton
Copy link
Member

Causing our builds to fail.

I have no idea why ;_;
@alexcrichton alexcrichton added the A-spurious Area: Spurious failures in builds (spuriously == for no apparent reason) label Mar 8, 2017
This was referenced Mar 8, 2017
Merged
Closed
@alexcrichton
Copy link
Member Author

According to https://travis-ci.org/rust-lang/rust/jobs/209124004:

  • We have 30GB of disk space 23 of which is available on the start of a build:

    Filesystem      Size  Used Avail Use% Mounted on
none             30G  5.7G   23G  20% /

  • At the end of the build, the obj/build dir is 23 GB:

    $ du -sbh obj/*
23G	obj/build

And such, we're filling up.

@alexcrichton
Copy link
Member Author

cc #40371

@alexcrichton
Copy link
Member Author

According to https://travis-ci.org/rust-lang/rust/jobs/209140948 we start out with 5/30GB taken up

@alexcrichton
Copy link
Member Author

Word from travis is that we can't increase disk size right now.

@alexcrichton
Copy link
Member Author

According to https://s3.amazonaws.com/archive.travis-ci.org/jobs/209178163/log.txt the run-pass output directory is 17GB

@alexcrichton
Copy link
Member Author

"Hello world" for musl is 3.5 MB. With 2.8k tests and three separate targets being tested, that's ~30GB. That's where the space is going.

@alexcrichton
Copy link
Member Author

3.1MB of that 3.5 is debuginfo

@alexcrichton alexcrichton mentioned this issue Mar 9, 2017
Merged
@alexcrichton alexcrichton mentioned this issue Mar 9, 2017
Merged
alexcrichton added a commit to alexcrichton/rust that referenced this issue Mar 9, 2017
@alexcrichton
travis: Split the linux-tested-targets builder
f44801c 
Travis only gives us 30GB disk space and we don't currently have an option to
increase that. Each musl target generates "hello world" binaries of about 3.5MB
in size, and we're testing two targets in the same image. We have around 3k
run-pass tests and 2 musl targets which works out to around 20GB. That's
dangerously close to the limit and is causing PRs to bounce.

This PR splits up the builder in two, one for x86_64 musl and the other for
i686. Hopefully that'll keep us under the disk limit.

Closes rust-lang#40359
bors added a commit that referenced this issue Mar 9, 2017
@bors
Auto merge of #40382 - alexcrichton:split-tested-targets, r=brson
ec87925 
travis: Split the linux-tested-targets builder

Travis only gives us 30GB disk space and we don't currently have an option to
increase that. Each musl target generates "hello world" binaries of about 3.5MB
in size, and we're testing two targets in the same image. We have around 3k
run-pass tests and 2 musl targets which works out to around 20GB. That's
dangerously close to the limit and is causing PRs to bounce.

This PR splits up the builder in two, one for x86_64 musl and the other for
i686. Hopefully that'll keep us under the disk limit.

Closes #40359
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
A-spurious Area: Spurious failures in builds (spuriously == for no apparent reason)
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

travis: Split the linux-tested-targets builder alexcrichton/rust
1 participant
@alexcrichton