{"push_id":1115367073,"size":1,"distinct_size":1,"ref":"refs/heads/master","head":"a40059d3a21aeb3c4593bf16ac0c3da0278fad8c","before":"303d8618d45336d8abd78411646a6e89b6d83bc8","commits":[{"sha":"a40059d3a21aeb3c4593bf16ac0c3da0278fad8c","author":{"email":"ff03357d67bcebc26cfe1ba3e1cd0340adfee2af@activeeon.com","name":"fviale"},"message":"Low priority tasks can be scheduled over high priority ones #2544\n\nWhen calling getRMNodes() in the scheduling loop, the set of nodes available on the resource manager at this moment can differ from the set of nodes which were available at the beginning of the loop.\n\n Accordingly, a low priority task can take this opportunity to schedule before higher priority ones\n\nThis change :\n- memorize inside the loop the expected number of nodes available\n- breaks the loop if the actual resource manager state differs from the expected\n- adds a complex test which tries to create a large number of nodes inside a scheduling loop in order to reproduce the issue","distinct":true,"url":"https://api.github.com/repos/fviale/scheduling/commits/a40059d3a21aeb3c4593bf16ac0c3da0278fad8c"}]}