Nemesis tests power off datacenter or bridge_pile #21100
Conversation
|
⚪ Test history | Ya make output | Test bloat
🟢
*please be aware that the difference is based on comparing your commit and the last completed build from the post-commit, check comparation |
|
🟢 |
|
⚪ Test history | Ya make output | Test bloat
⚪ Test history | Ya make output | Test bloat | Test bloat
⚪ Test history | Ya make output | Test bloat | Test bloat | Test bloat
🟢
*please be aware that the difference is based on comparing your commit and the last completed build from the post-commit, check comparation |
|
⚪ Test history | Ya make output | Test bloat
🟢
*please be aware that the difference is based on comparing your commit and the last completed build from the post-commit, check comparation |
|
⚪ Test history | Ya make output | Test bloat
⚪ Test history | Ya make output | Test bloat | Test bloat
🟡
*please be aware that the difference is based on comparing your commit and the last completed build from the post-commit, check comparation |
| self._bridge_pile_cycle = self._create_bridge_pile_cycle() | ||
| self._bridge_clients = self._create_bridge_clients() | ||
|
|
||
| def next_schedule(self): |
There was a problem hiding this comment.
Уже было выше, вроде
|
|
||
| self.logger.info("=== MANAGING BRIDGE STATE ===") | ||
| try: | ||
| self._manage_bridge_state() |
There was a problem hiding this comment.
При тестировании с немезисом процесс шатания запускается на каждом хосте кластера. Не получится ли здесь ситуация, что два процесса начнут отправлять совсем странные вещи в один и тот же пайл?
Changelog entry
Nemesis tests power off datacenter or bridge_pile
Changelog category
Description for reviewers
...