{"push_id":705058807,"size":1,"distinct_size":1,"ref":"refs/heads/master","head":"2319d02942d79d6d3abe3f9ab43002c91146a8e5","before":"41f900f52d7723f9243ee48f001b1c5da3b07a5d","commits":[{"sha":"2319d02942d79d6d3abe3f9ab43002c91146a8e5","author":{"email":"639072f68156d91c9bc11d6834444a8095641773@redhat.com","name":"Ido Barkan"},"message":"net: tests: wait for a specific state of a device\n\n5d6c571d added _waitForKnownOperstate. This improved tests\nreliability but it is not enough. It may happen that a test will\nfail because the initial device state is down and inside a\nnonChangingOperstate context manager, it changes to up. It is safer\nto ensure that the initial operation state is not only other than\n'unknown' but a specific one (most probably 'up').\nAlso, the state names where replaced with constants in\nlib/vdsm/netinfo.py for future use.\n\nChange-Id: Icbcfe6423894b2b8806c355dd093ddfd66eb75f0\nSigned-off-by: Ido Barkan <ibarkan@redhat.com>\nReviewed-on: https://gerrit.ovirt.org/42675\nReviewed-by: Dan Kenigsberg <danken@redhat.com>\nContinuous-Integration: Jenkins CI","distinct":true,"url":"https://api.github.com/repos/oVirt/vdsm/commits/2319d02942d79d6d3abe3f9ab43002c91146a8e5"}]}