Just a quick follow up, that I could resolve the issue. Maybe this helps
someone in the future.
$BASH_ENV was pointing to a deprecated script, resetting the module
environment. This only is an issue for non-interactive, non-login shells (i.e.
sbatch) and the issue was therefore not seen when r
On 3/31/22 11:25, GHui wrote:
Sometimes when I run sbatch to submit a job, it doesn't output anything.
But when I run squeue, the job is running.
Because of this, If I submit many times, I missed the jobs which I submitted.
Which Slurm version do you run? Use "sinfo --version" to find out.
Yo
Is using "#!/bin/bash -l" enough to make it work?
On Thu, Mar 31, 2022 at 6:46 AM Sebastian Potthoff <
s.potth...@uni-muenster.de> wrote:
> Just a quick follow up, that I could resolve the issue. Maybe this helps
> someone in the future.
>
> $BASH_ENV was pointing to a deprecated script, resetti
We noticed that we can pass --cpu_bind into an srun commandline, but not
sbatch. Why is that?
Thanks
David
If I were to hazard a guess, I would say that srun actually runs things
whereas sbatch submits and runs a batch command.
How would sbatch get 'hostname' to run on a particular cpu?
Within sbatch, you could do that by using srun to run 'hostname'.
So it is the execution step that is where you woul
