Make advanced reservations work properly with core specialization.
Prior logic used to create an advanced reservation based upon a core count would ignore the specialized cores. Then when a job tried to use the reservation, it would consider the specialized cores and not be able to use the core count used in the reservation creation. This change considers specialized cores when creating the reservation.
Please register or sign in to comment