I would submit a bug on this just to inquire as to if there is any
replacement or option for FastSchedule 0. They may have suggestions.
-Paul Edmon-
On 11/6/19 3:16 AM, Taras Shapovalov wrote:
Hi Chris,
Thanks for the answer.
Does this mean that there is no way to get rid of annoying error
Hi Chris,
Thanks for the answer.
Does this mean that there is no way to get rid of annoying error messages
in the logs if we need the hardware autodetection (FastSchedule=0)?
error: FastSchedule will be removed in 20.02, as will the
FastSchedule=0 functionality. Please consider removing this from
On 5/11/19 6:36 am, Taras Shapovalov wrote:
Since Slurm 19.05.3 we get an error message that FastSchedule is
deprecated. But I cannot find in the documentation what is an
alternative option for FastSchedule=0. Do you know how we can do that
without using the option since 19.05.3?
There isn't
Hey guys,
Since Slurm 19.05.3 we get an error message that FastSchedule is
deprecated. But I cannot find in the documentation what is an alternative
option for FastSchedule=0. Do you know how we can do that without using the
option since 19.05.3?
Best regards,
Taras
