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

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

Comments

Projects
None yet
3 participants
@shaneknapp
Contributor

shaneknapp commented May 23, 2016

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

This comment has been minimized.

Show comment
Hide comment
@heuermh

heuermh May 23, 2016

Member

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

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

This comment has been minimized.

Show comment
Hide comment
@shaneknapp

shaneknapp May 23, 2016

Contributor

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

Contributor

shaneknapp commented May 23, 2016

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 referenced this issue Jul 20, 2016

Open

Release ADAM version 1.0.0 #1089

4 of 15 tasks complete

fnothaft added a commit to fnothaft/adam that referenced this issue Aug 25, 2016

[ADAM-1038] Eliminate writing to /tmp during CI builds.
Resolves #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 added a commit to fnothaft/adam that referenced this issue Aug 25, 2016

[ADAM-1038] Eliminate writing to /tmp during CI builds.
Resolves #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 closed this in ed882c0 Aug 25, 2016

heuermh added a commit to heuermh/adam that referenced this issue Sep 27, 2016

[ADAM-1038] Eliminate writing to /tmp during CI builds.
Resolves #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