Section outline

  • When a batch job runs, its stdout and stderr are captured into a file in the directory you submitted from, named slurm-<JOBID>.out by default.

    $ ls
example-job.sh  slurm-14738683.out

    Inside that file you'll find: the node the job ran on, your script's own output, accounting (CPU-hours consumed against the project), wallclock vs CPU time, exit status, and a memory summary.

    Wallclock time is real elapsed time. CPU time is the time the CPU was actively running your code. A 2-minute wallclock job that mostly waits on I/O might only consume a few seconds of CPU; a 2-minute job using 4 cores at 100% consumes ~8 CPU-minutes.

    If your script fails partway through, the error message lands in the same file — useful for post-mortem when you can't watch the job live.

    Read the canonical section →

    • Quiz: Inspect the output
      Students must
      Mark as done

      What ends up in slurm-*.out, and what wallclock time means.