{"push_id":716054616,"size":2,"distinct_size":2,"ref":"refs/heads/wharemap_eval","head":"a00972ac9b21c5cbb954b382249fea169c676df5","before":"549ffe4595bf0efd1c2815146f0b293c6334045c","commits":[{"sha":"3bcb969dccb3072ad570cfcab2e6323c31abc0f1","author":{"email":"7e2ae53e8504663075a98ac161bd6d604861acb0@srcf.ucam.org","name":"Malte Schwarzkopf"},"message":"Add a note as to why we're not setting costs in ConfigureResourceLeafNode.\n\nIt is not immediately obvious why we don't call into the cost model to\nobtain ResourceNodeToResourceNodeCost here; this change adds a comment\nexplaining why.\n\nAffected modules: scheduling/flow\n\nChange-Id: Ic916a3918c8c84f561aadd0e3f46e1b1ed6b540b","distinct":true,"url":"https://api.github.com/repos/ms705/firmament/commits/3bcb969dccb3072ad570cfcab2e6323c31abc0f1"},{"sha":"a00972ac9b21c5cbb954b382249fea169c676df5","author":{"email":"7e2ae53e8504663075a98ac161bd6d604861acb0@srcf.ucam.org","name":"Malte Schwarzkopf"},"message":"Invoke cost models' stats update iteration before the first solver iteration, too.\n\nPreviously, any cost model-specific cost updates within the resource\ntopology would only be applied after the first scheduling iteration,\nmeaning that the first job submitted after coordinator startup would not\nsee these costs. This change fixes this bug.\n\nAffected modules: scheduling/flow\n\nChange-Id: Ie3767f431a65ca14aa7cdb8ca2de2a8be4997076","distinct":true,"url":"https://api.github.com/repos/ms705/firmament/commits/a00972ac9b21c5cbb954b382249fea169c676df5"}]}