-
Notifications
You must be signed in to change notification settings - Fork 15
tests: Add network test with many nodes #65
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: main
Are you sure you want to change the base?
Conversation
Documentation for this PR has been generated and is available at: https://n0-computer.github.io/iroh-gossip/pr/65/docs/iroh_gossip/ Last updated: 2025-05-20T12:06:51Z |
Simulation report
Last updated: 2025-05-20T12:07:07Z |
d956b94
to
549bec9
Compare
a893707
to
130d5dc
Compare
549bec9
to
b1b5ee7
Compare
130d5dc
to
9fc90bd
Compare
b1b5ee7
to
b4abbd4
Compare
9fc90bd
to
9d0a324
Compare
9d0a324
to
cfefa65
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
minor comments otherwise lgtm :) is the ci timeout expected tho?
} | ||
|
||
#[tokio::test(flavor = "multi_thread")] | ||
async fn gossip_net_big() -> TestResult { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is a large enough test to merit some docs on its own. Could you describe first the setup (topology, number of nodes, churn, loss, etc, - you know the deal - plus listing what the env parameters are and what they mean in the context of the test) and then what it's asserting happens or does not happen?
.map(|x| x.parse().unwrap()) | ||
.unwrap_or(10000); | ||
let timeout = Duration::from_millis(timeout_ms); | ||
info!("recv timeout: {timeout:?}"); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
is this supposed to have logs?I don't see anything initializing the logger and I ran this with RUST_LOG=debug
, --nocapture
too and got nothing
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I readded the logging. I guess I removed it on accident inbetween.
cfefa65
to
a80bf1b
Compare
b4abbd4
to
1c521b9
Compare
This adds a large integration test that bootstraps a swarm with many nodes and lets each node broadcast some messages. The test runs with 100 nodes and 2 messages per node. On my machine I ran it a couple of times with 1000 nodes in release mode. It completes fine, but takes a while in debug mode, thus limited to 100 nodes for now to not overwhelm CI.
a80bf1b
to
51218d1
Compare
This adds a large integration test that bootstraps a swarm with many nodes and lets each node broadcast some messages. The test runs with 100 nodes and 2 messages per node. On my machine I ran it a couple of times with 1000 nodes in release mode. It completes fine, but takes a while in debug mode, thus limited to 100 nodes for now to not overwhelm CI.
51218d1
to
d1ec336
Compare
It isn't. I will need to dig in why it fails on cross and times out on windows. |
Description
Based on #53 and #64
This adds a large integration test that bootstraps a swarm with many nodes and lets each node broadcast some messages.
The test runs with 100 nodes and 2 messages per node.
On my machine I ran it a couple of times with 1000 nodes in release mode, completes fine, but takes a while in debug mode, thus limited to 100 nodes for now to not overwhelm CI.
Breaking Changes
Notes & open questions
Change checklist