-
Notifications
You must be signed in to change notification settings - Fork 639
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
e2e: Switch to a default network node count of 2 #1928
Conversation
e2e execution is at a new low of 7m (usually ranges between 8-10m). |
@@ -28,7 +28,7 @@ import ( | |||
) | |||
|
|||
const ( | |||
DefaultNodeCount = 5 | |||
DefaultNodeCount = 2 // Minimum required to ensure connectivity-based health checks will pass |
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.
even numbers give me the creeps :) How does 3 look?
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'm not sure how to quantify your discomfort. Is it more than consensus convention? I don't think we're expecting scenarios in a standard e2e job that require more than the minimum number of nodes. And fwiw, this is just the default and doesn't preclude using however many nodes make sense for consensus-focused testing.
Why this should be merged
The current default of 5 nodes requires more resources and slows down test execution on resource-constrained CI workers.
How this works
Default test networks to 2 nodes.
How this was tested
CI