{"push_id":1306440712,"size":1,"distinct_size":1,"ref":"refs/heads/dev/EE-1.9-SP","head":"9fea43eb235c471075e97b377faa89aef9b41c3f","before":"a219cd6dfff2ef1d491fd1af76ee6feb47ad99fa","commits":[{"sha":"9fea43eb235c471075e97b377faa89aef9b41c3f","author":{"name":"Amrith Kumar","email":"5047ff46d29451108541208a9542e36c98cfdff4@tesora.com"},"message":"Skip 'eject valid master' replication test\n\nThere is a test to eject a valid master during replication that is\nfailing more and more often in the scenario tests. Basically the\neject will only work if the heartbeat from the current master is\nmore than a minute old. This shouldn't happen in the scenario\ntest run, but it does - quite often.\n\nSince this is consuming a large amount of gate resources, and the\nbug isn't that onerous (but is probably hard to fix), the current\n'eject valid master' test will be turned off until the fix lands.\n\nThe scenario test will print out the bug number during each run\nas a reminder (using the new SkipKnownBug method).\n\nCo-Authored-By: Peter Stachowski <peter@tesora.com>\nCo-Authored-By: Amrith Kumar <amrith@tesora.com>\nAuthor:     Peter Stachowski <peter@tesora.com>\nRelated-Bug: #1622014\n(cherry picked from commit 7d8d743d8e168f64fa893c975d7301507d4985d8)\nConflicts:\n\ttrove/tests/scenario/runners/replication_runners.py\n\ttrove/tests/scenario/runners/test_runners.py\n\nConflicts:\n\ttrove/tests/scenario/runners/replication_runners.py\n\nChange-Id: Ic4ce86143794f03dff9d05fc7afc312ab4707ed0","distinct":true,"url":"https://api.github.com/repos/Tesora/tesora-trove/commits/9fea43eb235c471075e97b377faa89aef9b41c3f"}]}
{"actor":{"display_login":"tesora-gerrit"}}