Known issues: Difference between revisions

Known issues (view source)

506 bytes removed , 5 years ago

whole-node jobs and --export=none appear on scheduler pages, and not considered defects

Bureaucrats, cc_docs_admin, cc_staff

2,774

edits

@@ Line 11: / Line 11: @@
 <!--T:14-->
-* The CC Slurm configuration encourages whole-node jobs. When appropriate, users should request whole-node rather than per-core resources. Read about [[Job_scheduling_policies#Whole_nodes_versus_cores|whole node scheduling]].
+No known issues at this time.
-* 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.
 == Quota and filesystem problems == <!--T:7-->