Known issues: Difference between revisions

Jump to navigation Jump to search
no edit summary
No edit summary
No edit summary
Line 8: Line 8:


== Scheduler issues == <!--T:6-->
== Scheduler issues == <!--T:6-->
* Interactive jobs started via <tt>salloc</tt> do not support X11 forwarding. [[User:Mboisson|Maxime Boissonneault]] ([[User talk:Mboisson|talk]]) 18:37, 13 December 2017 (UTC)
* Interactive jobs started via <tt>salloc</tt> do not support X11 forwarding. (''Reported at 18:37, 13 December 2017 UTC'')
* The CC Slurm configuration encourages whole-node jobs. When appropriate, users should request whole-node rather than per-core resources. See [[Job_scheduling_policies#Whole_nodes_versus_cores;|Job Scheduling - Whole Node Scheduling]].
* The CC Slurm configuration encourages whole-node jobs. When appropriate, users should request whole-node rather than per-core resources. See [[Job_scheduling_policies#Whole_nodes_versus_cores;|Job Scheduling - Whole Node Scheduling]].
* By default, the job receives environment settings from the submitting shell. This can lead to irreproducible results if it's not what you expect. To force the job to run with a fresh-like login environment, you can submit with <tt>--export=none</tt> or add <tt>#SBATCH --export=NONE</tt> to your job script.
* By default, the job receives environment settings from the submitting shell. This can lead to irreproducible results if it's not what you expect. To force the job to run with a fresh-like login environment, you can submit with <tt>--export=none</tt> or add <tt>#SBATCH --export=NONE</tt> to your job script.
rsnt_translations
53,729

edits

Navigation menu