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
We want to make sure that Holochain startup time is reasonable. For some context, we used to require the cell to join its network before allowing zome calls, so we could have very slow startup times from Holochain starting to cells being ready (i.e. responding to zome calls). We want to make sure that there's nothing like this that can't be sped up on the startup path.
At the moment, Wind Tunnel cannot startup a Holochain conductor. That's something we're going to want to support for tests that need to stop/start conductors to simulate agents coming and going in long running tests. If that hasn't been implemented by the time we get to this issue then that will be a per-requisite to writing this scenario.
Placing in the WT MVP initially, if we can find time for this then it'd be a good piece of functionality to cover as part of the initial Wind Tunnel testing
Consider solving the problem of starting the conductor from WT in #132. Then implement this after Nomad is ready so we don't have an extra TryCP test to port
We want to make sure that Holochain startup time is reasonable. For some context, we used to require the cell to join its network before allowing zome calls, so we could have very slow startup times from Holochain starting to cells being ready (i.e. responding to zome calls). We want to make sure that there's nothing like this that can't be sped up on the startup path.
At the moment, Wind Tunnel cannot startup a Holochain conductor. That's something we're going to want to support for tests that need to stop/start conductors to simulate agents coming and going in long running tests. If that hasn't been implemented by the time we get to this issue then that will be a per-requisite to writing this scenario.Created based on Holochain issue #2414
The text was updated successfully, but these errors were encountered: