Hi Ole,
Ole Holm Nielsen writes:
> Hi Loris,
>
> On 9/26/22 12:51, Loris Bennett wrote:
>>> When designing restriction in job_submit.lua, I found there is no member in
>>> job_desc struct can directly be used to determine the node number finally
>>> allocated to a job. The job_desc.min_nodes s
Hi Loris,
On 9/26/22 12:51, Loris Bennett wrote:
When designing restriction in job_submit.lua, I found there is no member in
job_desc struct can directly be used to determine the node number finally
allocated to a job. The job_desc.min_nodes seem to
be a close answer, but it will be 0xFFFE
writes:
> Hi all:
>
>
>
> When designing restriction in job_submit.lua, I found there is no member in
> job_desc struct can directly be used to determine the node number finally
> allocated to a job. The job_desc.min_nodes seem to
> be a close answer, but it will be 0xFFFE when user not s
On 9/26/22 08:48, taleinterve...@sjtu.edu.cn wrote:
When designing restriction in job_submit.lua, I found there is no member
in job_desc struct can directly be used to determine the node number
finally allocated to a job. The *job_desc.min_nodes *seem to be a close
answer, but it will be 0x
Hi all:
When designing restriction in job_submit.lua, I found there is no member in
job_desc struct can directly be used to determine the node number finally
allocated to a job. The job_desc.min_nodes seem to be a close answer, but it
will be 0xFFFE when user not specify -node option. The
