Sorry, I wasn't clear about that. The "--cpus-per-task" is custom work I did to try and enable that as a specification. I've sent a patch to them, but I haven't heard back and it doesn't look like its been worked in (good thing too, right?) At this point I think I'm kind of on my own to make this work.
Best M On Thu, Mar 27, 2014 at 10:16 AM, E V <[email protected]> wrote: > > Looking at the slurm-drmaa web > page(http://apps.man.poznan.pl/trac/slurm-drmaa) under the Native > Specification header, I don't see cpus-per-task listed as one of the > supported specs, and indeed when I tried it using > ruby-drmaa->slurm-drmaa it tells me it's an invalid native spec. So it > seems slurm-drmaa would be the place to go. > > On Thu, Mar 27, 2014 at 10:40 AM, Michael Gutteridge > <[email protected]> wrote: >> >> Hi >> >> Got a bit of a hairy problem. Slurm 2.6.2, MWM 7.2.6 doing the >> scheduling with the wiki2 plugin. We have tools using DRMAA to submit >> jobs: python-drmaa->slurm-drmaa->slurm >> >> I recently added '--cpus-per-task' to the native specifications >> supported by slurm-drmaa. I apparently have more work to do as jobs >> aren't properly created- the job doesn't have NumCPUs set properly: >> >> NumNodes=1 NumCPUs=1 CPUs/Task=2 ReqS:C:T=*:*:* >> MinCPUsNode=2 MinMemoryNode=0 MinTmpDiskNode=0 >> >> This is giving Moab a headache- it reports 0 tasks for the job and >> refuses to run it. >> >> So anyway- I don't know if it's a slurm or slurm-drmaa issue- I'd like >> to fix this, but I'm unsure of the proper place to implement the >> repair. Where is the NumCPUs calculation done? Is there something in >> the API I should use or is the API supposed to be doing that >> calculation? >> >> Any hints appreciated. >> >> Thanks >> >> Michael -- Hey! Somebody punched the foley guy! - Crow, MST3K ep. 508
