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
chore: swarm executor should match runtime in tests
We've changed most of our tests to use the `tokio` runtime: libp2p#4449.
All of these tests, however, were using `swarm_test::Swarm::new_ephemeral`, which actually creates a `Swarm` with `async_std` executor.
This PR changes all test that are using tokio as runtime to use `swarm_test::Swarm::new_ephemeral_tokio`, so that the executor used by the swarm matches the test's executor.
It also defaults `swarm-test` to the `tokio` feature.
Pull-Request: libp2p#6024.
libp2p-stream = { version = "0.3.0-alpha.1", path = "protocols/stream" }
105
105
libp2p-swarm = { version = "0.47.0", path = "swarm" }
106
106
libp2p-swarm-derive = { version = "=0.35.1", path = "swarm-derive" } # `libp2p-swarm-derive` may not be compatible with different `libp2p-swarm` non-breaking releases. E.g. `libp2p-swarm` might introduce a new enum variant `FromSwarm` (which is `#[non-exhaustive]`) in a non-breaking release. Older versions of `libp2p-swarm-derive` would not forward this enum variant within the `NetworkBehaviour` hierarchy. Thus the version pinning is required.
107
-
libp2p-swarm-test = { version = "0.5.0", path = "swarm-test" }
107
+
libp2p-swarm-test = { version = "0.6.0", path = "swarm-test" }
108
108
libp2p-tcp = { version = "0.43.0", path = "transports/tcp" }
109
109
libp2p-tls = { version = "0.6.2", path = "transports/tls" }
110
110
libp2p-uds = { version = "0.42.0", path = "transports/uds" }
0 commit comments