PR to track down CI failures (#501)

* Use an extended timeout for DKGs specifically

* Add a log statement when message-queue connection fails

* Add a 60 second keep-alive to connections

* Use zalloc for processor/message-queue/coordinator

An additional layer which protects us against edge cases with Zeroizing
(objects which don't support it or don't miss it).

* Add further logs to message-queue

* Further increase re-attempt timeouts in CI

* Remove misplaced continue inmessage-queue client

Fixes observed CI failures.

* Revert "Further increase re-attempt timeouts in CI"

This reverts commit 3723530cf6.
This commit is contained in:
Luke Parker
2024-01-04 01:08:13 -05:00
committed by GitHub
parent 6c8040f723
commit 7eb388e546
10 changed files with 63 additions and 15 deletions

3
Cargo.lock generated
View File

@@ -7344,6 +7344,7 @@ dependencies = [
"sp-runtime",
"tokio",
"tributary-chain",
"zalloc",
"zeroize",
]
@@ -7486,6 +7487,7 @@ dependencies = [
"serai-env",
"serai-primitives",
"tokio",
"zalloc",
"zeroize",
]
@@ -7607,6 +7609,7 @@ dependencies = [
"sp-application-crypto",
"thiserror",
"tokio",
"zalloc",
"zeroize",
]