Skip to content
GitLab
Explore
Sign in
Primary navigation
Search or go to…
Project
P
Partage de connaissances
Manage
Activity
Members
Labels
Plan
Issues
Issue boards
Milestones
Iterations
Wiki
Requirements
Code
Merge requests
Repository
Branches
Commits
Tags
Repository graph
Compare revisions
Snippets
Locked files
Build
Pipelines
Jobs
Pipeline schedules
Test cases
Artifacts
Deploy
Releases
Package registry
Container registry
Model registry
Operate
Environments
Terraform modules
Monitor
Incidents
Analyze
Value stream analytics
Contributor analytics
CI/CD analytics
Repository analytics
Code review analytics
Issue analytics
Insights
Model experiments
Help
Help
Support
GitLab documentation
Compare GitLab plans
GitLab community forum
Contribute to GitLab
Provide feedback
Keyboard shortcuts
?
Snippets
Groups
Projects
Show more breadcrumbs
ImaLang
Partage de connaissances
Commits
0e7070c8
Commit
0e7070c8
authored
Mar 3, 2024
by
Francois Ledoyen
Browse files
Options
Downloads
Patches
Plain Diff
add slurm inspect job
parent
4c73ef6c
No related branches found
No related tags found
No related merge requests found
Pipeline
#26881
passed
Mar 3, 2024
Stage: deploy
Changes
1
Pipelines
1
Show whitespace changes
Inline
Side-by-side
Showing
1 changed file
src/hpc_guide/slurm.md
+15
-2
15 additions, 2 deletions
src/hpc_guide/slurm.md
with
15 additions
and
2 deletions
src/hpc_guide/slurm.md
+
15
−
2
View file @
0e7070c8
...
@@ -4,6 +4,18 @@ order: 1
...
@@ -4,6 +4,18 @@ order: 1
# SLURM guide
# SLURM guide
## Inspect running job
You can further inspect a running job by connecting to it with this command :
```
sh
srun
--jobid
=
jobid
--overlap
--pty
bash
```
This will open an interactive shell as a job step under an already allocated
job. I.e. you will be able to see how your job is behaving. For distributed
memory jobs you will get a shell at the first node used by your job.
## Debug in Real-time on SLURM
## Debug in Real-time on SLURM
### Problem
### Problem
...
@@ -15,7 +27,7 @@ process. It goes something like this :
...
@@ -15,7 +27,7 @@ process. It goes something like this :
1.
Check for errors/change code.
1.
Check for errors/change code.
1.
Repeat endlessly until your code works.
1.
Repeat endlessly until your code works.
### Solution
### Solution
: interactive jobs (`srun --pty`)
Fortunately, there’s a better way, you can debug in real-time like so:
Fortunately, there’s a better way, you can debug in real-time like so:
...
@@ -35,6 +47,7 @@ Fortunately, there’s a better way, you can debug in real-time like so:
...
@@ -35,6 +47,7 @@ Fortunately, there’s a better way, you can debug in real-time like so:
1.
Check for errors/change code continuously until code is fixed or node has
1.
Check for errors/change code continuously until code is fixed or node has
timed out.
timed out.
##
#
Sources
## Sources
-
[
HPC-UiT Services User Documentation
](
https://hpc-uit.readthedocs.io/en/latest/jobs/interactive.html#starting-an-interactive-job
)
-
[
HPC-UiT Services User Documentation
](
https://hpc-uit.readthedocs.io/en/latest/jobs/interactive.html#starting-an-interactive-job
)
-
[
Innsbruck University's SLURM Tutorial
](
https://www.uibk.ac.at/zid/systeme/hpc-systeme/common/tutorials/slurm-tutorial.html
)
This diff is collapsed.
Click to expand it.
Preview
0%
Loading
Try again
or
attach a new file
.
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Save comment
Cancel
Please
register
or
sign in
to comment