-
Notifications
You must be signed in to change notification settings - Fork 293
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
test(e2e benchmark): refactors E2EThroughput #3395
Conversation
WalkthroughWalkthroughThe recent changes streamline the process for setting up nodes and running benchmark tests by introducing the Changes
Assessment against linked issues
The changes successfully consolidate test settings into the Recent Review DetailsConfiguration used: .coderabbit.yaml Files selected for processing (2)
Files skipped from review as they are similar to previous changes (2)
Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media? TipsChatThere are 3 ways to chat with CodeRabbit:
Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments. CodeRabbit Commands (invoked as PR comments)
Additionally, you can add CodeRabbit Configration File (
|
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.
Actionable comments posted: 0
Out of diff range and nitpick comments (2)
test/e2e/benchmark/throughput.go (1)
54-56
: Ensure error handling is robust and provides clear context for failures.Consider enhancing the error message to include more specific details about the failure context when creating a new benchmark test.
test/e2e/benchmark/manifest.go (1)
1-1
: Change of package declaration fromtestnet
tomain
is significant. Ensure this aligns with the project's architectural standards.
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.
Actionable comments posted: 1
blockchain, err := testnode.ReadBlockchain(context.Background(), | ||
benchTest.Node(0).AddressRPC()) |
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.
Use of context.Background()
in ReadBlockchain
might not be ideal for all scenarios. Consider passing a context that can be controlled externally.
- blockchain, err := testnode.ReadBlockchain(context.Background(),
+ ctx, cancel := context.WithTimeout(context.Background(), 30*time.Second)
+ defer cancel()
+ blockchain, err := testnode.ReadBlockchain(ctx,
Committable suggestion
‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation.
blockchain, err := testnode.ReadBlockchain(context.Background(), | |
benchTest.Node(0).AddressRPC()) | |
ctx, cancel := context.WithTimeout(context.Background(), 30*time.Second) | |
defer cancel() | |
blockchain, err := testnode.ReadBlockchain(ctx, | |
benchTest.Node(0).AddressRPC()) |
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.
utAck
A follow-up PR for #3391 that addresses and closes #3363.
Summary of changes:
The
BenchmarkTest
type has been introduced, inheriting all the behaviors of aTestnet
. Additionally, it encapsulates aManifest
that defines the test network topology, parameters, and configurations, etc., and directs the network formation.