Project

General

Profile

Feature #22410

Allow the user to define the location of the temporary storage used for fake jobsub.

Added by Jason Stock 8 months ago. Updated 4 months ago.

Status:
Closed
Priority:
Normal
Assignee:
-
Target version:
-
Start date:
04/18/2019
Due date:
% Done:

0%

Estimated time:
Duration:

Description

When trying to debug a setup issue with fake jobsub, I ran into a problem because fife_launch --fake uses /tmp. Since my job is installing a release from a tarball, I immediately fill /tmp (gpvms have only 2 G available) when doing so. Allowing the user to define the location of the TMPDIR for fake_jobsub in the fifelaunch command would remedy this issue.

History

#1 Updated by Marc Mengel 8 months ago

fake_jobsub should respect TMPDIR set in the environment.

export workdir=${TMPDIR:-/tmp}/fake_jobsub_work$$_`date +%s`

should use the value of TMPDIR defaulting to /tmp.

#2 Updated by Jason Stock 8 months ago

Thanks. Using `TMPDIR=<TMP_TEST_DIR> fife_launch -c .....` works great!

#3 Updated by Jason Stock 8 months ago

Fake 168181555621822.1 is pid 17001

Job output will be in /dune/app/users/jstock/20190411-ParticleInventoryArtSmartUpdate_
LarsimOnly/TMPTEST/fake_jobsub_work16818_1555621822

#4 Updated by Marc Mengel 4 months ago

  • Status changed from New to Closed


Also available in: Atom PDF