status-im
/
libp2p-test-plans
mirror of https://github.com/status-im/libp2p-test-plans.git
2
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity
libp2p-test-plans/ping/rust/Cargo.toml

37 lines
2.1 KiB
TOML
Raw Normal View History

ping/rust: introduce rust cross-version test (#26) * ping/go: fix composition name * ping/rust: introduce the ping/rust test * Showcase version selection through features Can be run with `cargo check --features libp2pv0450` or `cargo check --features libp2pv0440`. * Peer programming session * ping/rust: experiment with master & current groups * ping/rust/src/main: Simplify import across versions * ping/rust/src/main: Remove commented out code * ping/rust/src/main: Clean up * ping/rust/Dockerfile: Update crates.io index in separate step Potentially allows caching. * ping/rust/Dockerfile: Don't both build and install Building the binary in release mode is enough. * ping/rust/src/main: Clean up log lines * ping/rust: Implement iterations with latency * ping/rust/src/main: Extract signal and wait logic into fn * ping/rust/Dockerfile: import caching fixes * ping/: add cross-version composition * ping/rust: add json payloads fix * ping/rust: match iterations id with go * ping/rust/Dockerfile: improve caching * ci: introduce workflow ping-interop-rust * ping/interop: update latest versions * ping/_compositions: add full ping interop * ci: resolve git reference to sha * ping/rust/Dockerfile: drop cargo output * ping/rust: drop version indirection * ping/rust/Dockerfile: fix features to support caching * ping/rust/Dockerfile: do not cache the rewritten package * ping/_compositions/*: use concurrent_builds * ping/_compositions/*: drop test_instances count * ci: build composition then run * ping: introduce InteropTarget option * ci: fix interop target & build * ping/_compositions/*: introduce load_resource * ci: 10 minutes timeout for the run step * README: add update instruction for rust & clean go * ping/rust/Dockerfile: add protocol buffer compiler * ping/rust/Cargo.lock: cargo update packages * .github: increase testground timeout Co-authored-by: Max Inden <mail@max-inden.de>
2022-08-22 10:25:07 +00:00
[package]
edition = "2021"
name = "testplan"
version = "0.1.0"
[dependencies]
ping/rust: Refactor into multiple binaries (#72) By having one Rust binary per version, we can vary the actual binary from version to version and f.e. fix deprecated API calls. It does introduce a bit of duplication between the different versions but I'd rather have that then not being able to adapt the tests to new APIs. Instead of activating a feature per libp2p version, we add them all as dependencies. This ensures all transitive dependencies are properly tracked in `Cargo.lock`. Additionally, this gives us a single place we are can activate all the feature. For `master` and pull-request builds, we replace the git target or rev with the one coming from the CI build. Once we trigger a build, `cargo` will update and resolve the necessary dependencies before that, thus fixing problems such as https://github.com/libp2p/rust-libp2p/pull/2972.
2022-11-18 11:49:30 +00:00
async-trait = "0.1.58"
anyhow = "1"
async-std = { version = "1.10", features = ["attributes", "tokio1"] }
ping/rust: introduce rust cross-version test (#26) * ping/go: fix composition name * ping/rust: introduce the ping/rust test * Showcase version selection through features Can be run with `cargo check --features libp2pv0450` or `cargo check --features libp2pv0440`. * Peer programming session * ping/rust: experiment with master & current groups * ping/rust/src/main: Simplify import across versions * ping/rust/src/main: Remove commented out code * ping/rust/src/main: Clean up * ping/rust/Dockerfile: Update crates.io index in separate step Potentially allows caching. * ping/rust/Dockerfile: Don't both build and install Building the binary in release mode is enough. * ping/rust/src/main: Clean up log lines * ping/rust: Implement iterations with latency * ping/rust/src/main: Extract signal and wait logic into fn * ping/rust/Dockerfile: import caching fixes * ping/: add cross-version composition * ping/rust: add json payloads fix * ping/rust: match iterations id with go * ping/rust/Dockerfile: improve caching * ci: introduce workflow ping-interop-rust * ping/interop: update latest versions * ping/_compositions: add full ping interop * ci: resolve git reference to sha * ping/rust/Dockerfile: drop cargo output * ping/rust: drop version indirection * ping/rust/Dockerfile: fix features to support caching * ping/rust/Dockerfile: do not cache the rewritten package * ping/_compositions/*: use concurrent_builds * ping/_compositions/*: drop test_instances count * ci: build composition then run * ping: introduce InteropTarget option * ci: fix interop target & build * ping/_compositions/*: introduce load_resource * ci: 10 minutes timeout for the run step * README: add update instruction for rust & clean go * ping/rust/Dockerfile: add protocol buffer compiler * ping/rust/Cargo.lock: cargo update packages * .github: increase testground timeout Co-authored-by: Max Inden <mail@max-inden.de>
2022-08-22 10:25:07 +00:00
env_logger = "0.9.0"
if-addrs = "0.7.0"
log = "0.4"
rand = "0.8"
serde_json = "1"
soketto = "0.7.1"
ping/rust: Update rust-sdk patch, remove unused dependencies (#42) * ping/rust: remove unused dependencies * README: fix import instructions * ping/rust: set channel capacity to # of instances * ping/rust: use testground-v0.4.0 from crates.io
2022-10-04 11:42:33 +00:00
testground = "0.4.0"
ping/rust: introduce rust cross-version test (#26) * ping/go: fix composition name * ping/rust: introduce the ping/rust test * Showcase version selection through features Can be run with `cargo check --features libp2pv0450` or `cargo check --features libp2pv0440`. * Peer programming session * ping/rust: experiment with master & current groups * ping/rust/src/main: Simplify import across versions * ping/rust/src/main: Remove commented out code * ping/rust/src/main: Clean up * ping/rust/Dockerfile: Update crates.io index in separate step Potentially allows caching. * ping/rust/Dockerfile: Don't both build and install Building the binary in release mode is enough. * ping/rust/src/main: Clean up log lines * ping/rust: Implement iterations with latency * ping/rust/src/main: Extract signal and wait logic into fn * ping/rust/Dockerfile: import caching fixes * ping/: add cross-version composition * ping/rust: add json payloads fix * ping/rust: match iterations id with go * ping/rust/Dockerfile: improve caching * ci: introduce workflow ping-interop-rust * ping/interop: update latest versions * ping/_compositions: add full ping interop * ci: resolve git reference to sha * ping/rust/Dockerfile: drop cargo output * ping/rust: drop version indirection * ping/rust/Dockerfile: fix features to support caching * ping/rust/Dockerfile: do not cache the rewritten package * ping/_compositions/*: use concurrent_builds * ping/_compositions/*: drop test_instances count * ci: build composition then run * ping: introduce InteropTarget option * ci: fix interop target & build * ping/_compositions/*: introduce load_resource * ci: 10 minutes timeout for the run step * README: add update instruction for rust & clean go * ping/rust/Dockerfile: add protocol buffer compiler * ping/rust/Cargo.lock: cargo update packages * .github: increase testground timeout Co-authored-by: Max Inden <mail@max-inden.de>
2022-08-22 10:25:07 +00:00
thiserror = "1"
tokio = { version = "1", default-features = false, features = ["sync", "rt-multi-thread", "macros", "net"] }
tokio-stream = { version = "0.1", default-features = false, features = [] }
tokio-util = { version = "0.7", default-features = false, features = ["compat"] }
futures = "0.3.1"
ping/rust: Refactor into multiple binaries (#72) By having one Rust binary per version, we can vary the actual binary from version to version and f.e. fix deprecated API calls. It does introduce a bit of duplication between the different versions but I'd rather have that then not being able to adapt the tests to new APIs. Instead of activating a feature per libp2p version, we add them all as dependencies. This ensures all transitive dependencies are properly tracked in `Cargo.lock`. Additionally, this gives us a single place we are can activate all the feature. For `master` and pull-request builds, we replace the git target or rev with the one coming from the CI build. Once we trigger a build, `cargo` will update and resolve the necessary dependencies before that, thus fixing problems such as https://github.com/libp2p/rust-libp2p/pull/2972.
2022-11-18 11:49:30 +00:00
libp2pv0440 = { package = "libp2p", version = "0.44.0", default_features = false, features = ["websocket", "mplex", "yamux", "tcp-async-io", "ping", "noise", "dns-async-std"] }
ping: update Rust versions 0.45.0 and 0.46.0, (#76) to 0.45.1 and 0.46.1 respectively.
2022-11-23 14:49:54 +00:00
libp2pv0451 = { package = "libp2p", version = "0.45.1", default_features = false, features = ["websocket", "mplex", "yamux", "tcp-async-io", "ping", "noise", "dns-async-std"] }
libp2pv0461 = { package = "libp2p", version = "0.46.1", default_features = false, features = ["websocket", "mplex", "yamux", "tcp-async-io", "ping", "noise", "dns-async-std"] }
ping/rust: Refactor into multiple binaries (#72) By having one Rust binary per version, we can vary the actual binary from version to version and f.e. fix deprecated API calls. It does introduce a bit of duplication between the different versions but I'd rather have that then not being able to adapt the tests to new APIs. Instead of activating a feature per libp2p version, we add them all as dependencies. This ensures all transitive dependencies are properly tracked in `Cargo.lock`. Additionally, this gives us a single place we are can activate all the feature. For `master` and pull-request builds, we replace the git target or rev with the one coming from the CI build. Once we trigger a build, `cargo` will update and resolve the necessary dependencies before that, thus fixing problems such as https://github.com/libp2p/rust-libp2p/pull/2972.
2022-11-18 11:49:30 +00:00
libp2pv0470 = { package = "libp2p", version = "0.47.0", default_features = false, features = ["websocket", "mplex", "yamux", "tcp-async-io", "ping", "noise", "dns-async-std"] }
libp2pv0480 = { package = "libp2p", version = "0.48.0", default_features = false, features = ["websocket", "mplex", "yamux", "tcp-async-io", "ping", "noise", "dns-async-std", "rsa"] }
libp2pv0490 = { package = "libp2p", version = "0.49.0", features = ["websocket", "mplex", "yamux", "tcp", "async-std", "ping", "noise", "dns", "rsa"] }
ping/rust: Add 0.50.0 as a release and fix deprecation warnings (#87)
2022-12-01 16:14:22 +00:00
libp2pv0500 = { package = "libp2p", version = "0.50.0", features = ["websocket", "mplex", "yamux", "tcp", "async-std", "ping", "noise", "dns", "rsa", "macros"] }
ping/rust: remove the master dependency (#45) * ping/rust: pin sdk-rust version * ping/rust: make master branch explicit * ping/rust: drop version for master builds
2022-09-23 07:53:00 +00:00
ping/rust: Refactor into multiple binaries (#72) By having one Rust binary per version, we can vary the actual binary from version to version and f.e. fix deprecated API calls. It does introduce a bit of duplication between the different versions but I'd rather have that then not being able to adapt the tests to new APIs. Instead of activating a feature per libp2p version, we add them all as dependencies. This ensures all transitive dependencies are properly tracked in `Cargo.lock`. Additionally, this gives us a single place we are can activate all the feature. For `master` and pull-request builds, we replace the git target or rev with the one coming from the CI build. Once we trigger a build, `cargo` will update and resolve the necessary dependencies before that, thus fixing problems such as https://github.com/libp2p/rust-libp2p/pull/2972.
2022-11-18 11:49:30 +00:00
# Next release
ping/rust: Add 0.50.0 as a release and fix deprecation warnings (#87)
2022-12-01 16:14:22 +00:00
[dependencies."libp2pv0510"]
ping/rust: Refactor into multiple binaries (#72) By having one Rust binary per version, we can vary the actual binary from version to version and f.e. fix deprecated API calls. It does introduce a bit of duplication between the different versions but I'd rather have that then not being able to adapt the tests to new APIs. Instead of activating a feature per libp2p version, we add them all as dependencies. This ensures all transitive dependencies are properly tracked in `Cargo.lock`. Additionally, this gives us a single place we are can activate all the feature. For `master` and pull-request builds, we replace the git target or rev with the one coming from the CI build. Once we trigger a build, `cargo` will update and resolve the necessary dependencies before that, thus fixing problems such as https://github.com/libp2p/rust-libp2p/pull/2972.
2022-11-18 11:49:30 +00:00
package = "libp2p"
git = "https://github.com/libp2p/rust-libp2p"
ping/rust: Add 0.50.0 as a release and fix deprecation warnings (#87)
2022-12-01 16:14:22 +00:00
rev = "be0b62a78fe9d72811b9eda742137cc8ddc4da35" # This should usually point to a commit on master.
ping/rust: Refactor into multiple binaries (#72) By having one Rust binary per version, we can vary the actual binary from version to version and f.e. fix deprecated API calls. It does introduce a bit of duplication between the different versions but I'd rather have that then not being able to adapt the tests to new APIs. Instead of activating a feature per libp2p version, we add them all as dependencies. This ensures all transitive dependencies are properly tracked in `Cargo.lock`. Additionally, this gives us a single place we are can activate all the feature. For `master` and pull-request builds, we replace the git target or rev with the one coming from the CI build. Once we trigger a build, `cargo` will update and resolve the necessary dependencies before that, thus fixing problems such as https://github.com/libp2p/rust-libp2p/pull/2972.
2022-11-18 11:49:30 +00:00
features = ["websocket", "mplex", "yamux", "tcp", "ping", "noise", "dns", "async-std", "rsa", "macros"]