You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In e2e tests, before we make any client transfer, we grep the ledger's log for "Anoma ledger node started". After this, we proceed to test different ledger functionality.
Problem
When ran locally, most e2e tests seem to be failing arbitrarily. Upon closer inspection of log timestamps, we find that client requests are made, correctly, after "Anoma ledger node started" is logged, but not after "module=rpc-server msg="Starting RPC HTTP server on...", which happens after the RPC server service in Tendermint starts. All client transfers make RPC requests, therefore they fail with a TCP connection reset error.
Potential fix
Grep the Tendermint log for "Starting RPC HTTP server".
The text was updated successfully, but these errors were encountered:
Context
In e2e tests, before we make any client transfer, we grep the ledger's log for
"Anoma ledger node started"
. After this, we proceed to test different ledger functionality.Problem
When ran locally, most e2e tests seem to be failing arbitrarily. Upon closer inspection of log timestamps, we find that client requests are made, correctly, after
"Anoma ledger node started"
is logged, but not after"module=rpc-server msg="Starting RPC HTTP server on..."
, which happens after the RPC server service in Tendermint starts. All client transfers make RPC requests, therefore they fail with a TCP connection reset error.Potential fix
Grep the Tendermint log for "
Starting RPC HTTP server"
.The text was updated successfully, but these errors were encountered: