Comments (2)
This seems to be a pretty clear bug in how Slurm is setting up binding when you specify cpus-per-task (rzwhippet is running a newer version of Slurm than rzgenie). I'll report it to the Slurm developers so that we can get it fixed.
It looks like you can work around this by setting any valid '--cpu-bind' argument. E.g. here I set SLURM_CPU_BIND=quiet (which is the default cpu-bind behavior), and it rescues my simple reproducer.
[day36@rzwhippet17:salloc_test]$ cat runstuff.sh
#!/bin/sh
echo "#works"
SLURM_CPU_BIND=quiet srun --mpibind=off --nodes=1 --ntasks=1 --cpus-per-task=1 hostname
echo ""
echo "#fails"
srun --mpibind=off --nodes=1 --ntasks=1 --cpus-per-task=1 hostname
[day36@rzwhippet17:salloc_test]$ salloc -N2 --exclusive srun -N1 -n1 ./runstuff.sh
salloc: Granted job allocation 2365
salloc: Waiting for resource configuration
salloc: Nodes rzwhippet[16,22] are ready for job
#works
rzwhippet22
#fails
srun: error: CPU binding outside of job step allocation, allocated CPUs are: 0x00000000000000000000000000010000000000000000000000000001.
srun: error: Task launch for StepId=2365.2 failed on node rzwhippet22: Unable to satisfy cpu bind request
srun: error: Application launch failed: Unable to satisfy cpu bind request
srun: Job step aborted
srun: error: rzwhippet16: task 0: Exited with exit code 192
salloc: Relinquishing job allocation 2365
[day36@rzwhippet17:salloc_test]$
from ats.
Resolved, just have to teach folks to use --interactive after srun
salloc -N --exclusive srun --interactive -n 1
from ats.
Related Issues (20)
- Add ability to run a test on the same node as a previous test HOT 9
- Update --cutoff to over-ride per test job limits HOT 16
- Flux machine issues HOT 2
- Flux timeout marked as failure by ATS HOT 1
- Adjust Flux commands HOT 1
- per-test option cpusPerTask should work with the slurm module HOT 1
- Move Project Y to Current version of ATS and run using Flux on rzwhippet HOT 1
- Update lsf module to avoid using -N with -g option
- --smpi_off causes python codec errors HOT 1
- CPU and GPU jobs on same node HOT 6
- Ensure ATS can run CPU and GPU jobs concurrently on the same node with Flux
- atslite1 not passing through arguments correctly HOT 1
- lrun, old_default, and mpi_bind not happy HOT 1
- Multiple dependencies? HOT 1
- same node flux usaage (--requires=-rank:1) not working HOT 1
- Add support for Flux
- ATS does not return error codes on failed tests HOT 7
- Project install option broken? HOT 8
- add jsrun_np_max and lrun_np_max command line options
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from ats.