Running A Julia Script Through SLURM

General Usage
, , ,
2

Sounds strange…

I’m using a very similar setup, so the general idea should definitely work (create a Julia script with ArgParse and call it from the Slurm script).

  • In my experience, when salloc and sbatch do different things, it might be related to the shell environment, but not sure here since you start bash as a login shell and export the user environment explicitly. But perhaps you can check (e.g. by using the bash command env to print the whole environment and see if it differs somehow).
  • EDIT: Related to the first point: Is there anything in your .bashrc that could make the two cases behave differently?
  • Another useful step in debugging this problem would be to compare the output of versioninfo() and Pkg.status() in the Julia scripts. It looks like the same executable is called, but maybe the problem is in a specific version of Julia and/or the packages.
  • Are you using the global Julia environment? Have you tried creating a new environment in the script and adding your dependencies (ArgParse here) before you call the script. If the problem is related to (pre)compilation, this might help sorting it out.
  • Related to the compilation question: Are the machine CPUs identical? You specify intel18 in both, but I don’t know if there could be different details about the CPUs still?
  • Does the issue appear always on the same machine or on all machines (you could request a certain node explicitly to test that)?

Might be something completely unrelated :sweat_smile: but maybe checking these things can help narrow down the problem.

1 Like