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

[build system] ADAM test builds pollute /tmp, leaving lots of cruft... #1038

Closed
shaneknapp opened this issue May 23, 2016 · 2 comments
Closed

[build system] ADAM test builds pollute /tmp, leaving lots of cruft... #1038

shaneknapp opened this issue May 23, 2016 · 2 comments
Milestone
0.20.0

Comments

@shaneknapp
Copy link
Contributor

this is slowly filling up the disks on the jenkins workers. for example, ssh in to any of the amp-jenkins-[01..08] machines and take a look in /tmp.
@heuermh
Copy link
Member

heuermh commented May 23, 2016

Thanks for letting us know. Writing to /tmp (via the JDK's temporary file mechanism) in unit tests has been intentional on my part.

@shaneknapp
Copy link
Contributor Author

no problem... and don't worry, i'm not just singling out you guys. it's happening across many different product builds.

here's a ganglia graph of /tmp's disk usage on amp-jenkins-worker-01... you can see that in mid-may, i cleaned it (the spike in available space) and it filled up rather quickly afterwards.

tmp_nightmare

@fnothaft fnothaft added this to the 1.0.0 milestone Jul 20, 2016
@fnothaft fnothaft mentioned this issue Jul 20, 2016
Closed
15 tasks
fnothaft added a commit to fnothaft/adam that referenced this issue Aug 25, 2016
@fnothaft
[ADAM-1038] Eliminate writing to /tmp during CI builds.
b1e7f74 
Resolves bigdatagenomics#1038. When running `scripts/jenkins-test`, we make a temp dir where all
test files are written. We modify our `pom.xml`s at test time so that this temp
dir is passed as `java.io.tmpdir` when running scalatest, and then clean the temp
dir at the end of the CI build.
@fnothaft fnothaft mentioned this issue Aug 25, 2016
Closed
fnothaft added a commit to fnothaft/adam that referenced this issue Aug 25, 2016
@fnothaft
[ADAM-1038] Eliminate writing to /tmp during CI builds.
6e28504 
Resolves bigdatagenomics#1038. When running `scripts/jenkins-test`, we make a temp dir where all
test files are written. We modify our `pom.xml`s at test time so that this temp
dir is passed as `java.io.tmpdir` when running scalatest, and then clean the temp
dir at the end of the CI build.
heuermh pushed a commit to heuermh/adam that referenced this issue Sep 27, 2016
@fnothaft @heuermh
[ADAM-1038] Eliminate writing to /tmp during CI builds.
0fdf43f 
Resolves bigdatagenomics#1038. When running `scripts/jenkins-test`, we make a temp dir where all
test files are written. We modify our `pom.xml`s at test time so that this temp
dir is passed as `java.io.tmpdir` when running scalatest, and then clean the temp
dir at the end of the CI build.
@heuermh heuermh modified the milestones: 1.0.0, 0.20.0 Oct 13, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
0.20.0
Development

No branches or pull requests
3 participants
@heuermh @shaneknapp @fnothaft