Conversation
|
This is an automated comment for commit 47b5d13 with description of existing statuses. It's updated for the latest CI running
|
|
Isn't the failure you linked to because of after which there is a call I saw a lot of failures like this recently in stress tests. |
|
That's weird. The part was removed from ZooKeeper and from disk: But after restarting the server we found it in ZooKeeper: Will try to find which log message is lying... |
|
🤔 |
|
@antonio2368 I've noticed an exception about too much time spent by |
|
Stress tests were OK on the previous commit, failed integration tests are known to be flaky |
Changelog category (leave one):
See https://s3.amazonaws.com/clickhouse-test-reports/53087/369339f4d4aeb9045e94773b6dfd19a322df4a3b/stress_test__ubsan_/run.log