On 01/07/2022 15:05, Chris Samuel wrote:
> On 29/6/22 09:01, Jean-Christophe HAESSIG wrote:
>
>> No, the job is placed through DRMAA API which enables programs to place
>> jobs in a cluster-agnostic way. Th program doesn't know it is talking to
>> Slurm. The DRMAA library makes the translation and
On 1/7/22 07:51, Jean-Christophe HAESSIG wrote:
The libraries were incompatible but that wasn't reflected in the
packaging and due to the similar and long version string, I didn't spot
it before.
Oh good spot!
All the best,
Chris
--
Chris Samuel : http://www.csamuel.org/ : Berkeley, CA,
On 29/6/22 09:01, Jean-Christophe HAESSIG wrote:
No, the job is placed through DRMAA API which enables programs to place
jobs in a cluster-agnostic way. Th program doesn't know it is talking to
Slurm. The DRMAA library makes the translation and loads libslurm36,
where the messages comes from. Th
On 29/06/2022 15:01, Jean-Christophe HAESSIG wrote:
Hi,
Turns out I had libslurm36_20.11.7+really20.11.4-2+deb11u1 but
slurm-wlm-basic-plugins was only at version 20.11.7+really20.11.4
because libslurm36 was installed some time after the last Slurm upgrade.
The libraries were incompatible but t
Hi Miguel,
As far as I understood GrpTRESMins=cpu=N(4227) seems not to be the limit of the
QOS unlike its name but the RawUsage of the QOS in mn instead of second as
accounted in RawUsage.
When I set QOS RawUsage to 0 GrpTRESMins=cpu is also set to 0.
Each time a job as completed using this Q
