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
Instead of calling Env::default it creates a snapshot from scratch and converts that to an env. This fails to do a bunch of initialization that Env::default does for the testutils config, and also configures the initial snapshot with strange values for ttl etc.
Instead, the initial snapshot should be created with Env::default, subsequent time advances can still use snapshots to destroy and reconstruct the env.
The text was updated successfully, but these errors were encountered:
Using snapshots to destroy and recreate the environment may not be a good idea at all since Env::from_snapshot doesn't do the same test setup that Env::default does.
This example uses snapshots to reset the environment, but the way it initializes the first environment should not be recommended:
Instead of calling
Env::default
it creates a snapshot from scratch and converts that to an env. This fails to do a bunch of initialization thatEnv::default
does for the testutils config, and also configures the initial snapshot with strange values for ttl etc.Instead, the initial snapshot should be created with
Env::default
, subsequent time advances can still use snapshots to destroy and reconstruct the env.The text was updated successfully, but these errors were encountered: