Fix an IsFeasible bug where start and end of different reservations overlap.
When IsFeasible processes the list of events (i.e. reservation start/end, expt start/end), it processes them in sorted order of event time, but if times are equal, there is no secondary sort, and thus the additive (incoming) reservation might be processed before the reductive (outgoing) reservation), which would create a false negative hole in the forecast. This commit adds the secondary sort.
Showing with 9 additions and 2 deletions