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
Currently, we are using a chain-id == "private" for each test. Up to this point, this has worked perfectly, but now that we are collecting data to an external database for many different networks and tests, using a unique chain-id would allow us to easily distinguish between test runs/networks in that data base.
This was recently also changed in the tendermint e2e test in #970
The text was updated successfully, but these errors were encountered:
Currently, we are using a chain-id == "private" for each test. Up to this point, this has worked perfectly, but now that we are collecting data to an external database for many different networks and tests, using a unique chain-id would allow us to easily distinguish between test runs/networks in that data base.
This was recently also changed in the tendermint e2e test in #970
The text was updated successfully, but these errors were encountered: