yihuang commented 4 months ago

Solution:

tar the home directory into outputs volume

👮🏻👮🏻👮🏻 !!!! REFERENCE THE PROBLEM YOUR ARE SOLVING IN THE PR TITLE AND DESCRIBE YOUR SOLUTION HERE !!!! DO NOT FORGET !!!! 👮🏻👮🏻👮🏻

PR Checklist:

[ ] Have you read the CONTRIBUTING.md?
[ ] Does your PR follow the C4 patch requirements?
[ ] Have you rebased your work on top of the latest master?
[ ] Have you checked your code compiles? (make)
[ ] Have you included tests for any non-trivial functionality?
[ ] Have you checked your code passes the unit tests? (make test)
[ ] Have you checked your code formatting is correct? (go fmt)
[ ] Have you checked your basic code style is fine? (golangci-lint run)
[ ] If you added any dependencies, have you checked they do not contain any known vulnerabilities? (go list -json -m all | nancy sleuth)
[ ] If your changes affect the client infrastructure, have you run the integration test?
[ ] If your changes affect public APIs, does your PR follow the C4 evolution of public contracts?
[ ] If your code changes public APIs, have you incremented the crate version numbers and documented your changes in the CHANGELOG.md?
[ ] If you are contributing for the first time, please read the agreement in CONTRIBUTING.md now and add a comment to this pull request stating that your PR is in accordance with the Developer's Certificate of Origin.

Thank you for your code, it's appreciated! :)

Summary by CodeRabbit

New Features
- Enhanced documentation for setting up and executing a stateless mode for a cluster, including detailed descriptions of new command parameters.
- Added a new command for creating an output directory, improving data handling for node files.
- Updated benchmarking tool to allow configuration of the number of accounts and transactions, enhancing usability.
- Improved logging in transaction testing for better clarity and traceability.
Bug Fixes
- Simplified command execution in the service definitions for better functionality and clarity.

coderabbitai[bot] commented 4 months ago

Walkthrough

The recent changes significantly enhance the testground documentation and functionality, improving clarity for setting up stateless cluster tests. Key updates feature expanded command parameters for test cases, refined guidance on data directory management, and greater configurability in benchmarking tools. These modifications streamline user experience, promote better organization of output data, and ultimately support more effective testing processes.

Changes

Files	Change Summary
`testground/README.md`	Enhanced documentation on stateless mode setup, added parameters for test commands, clarified data directory commands, and introduced a new output directory for node data files.
`testground/benchmark/benchmark/stateless.py`	Updated `gen` function with new parameters for account and transaction numbers, centralized configuration management with a `config.json`, and modified `run` function to read from this configuration for load generation, enhancing configurability and usability.
`testground/benchmark/benchmark/sendtx.py`	Improved logging in `sendtx` function to provide better visibility into transaction processes without altering functionality.
`testground/benchmark/compositions/docker-compose.jsonnet`	Simplified command execution by removing specific arguments for accounts and transactions, added a `volumes` section to allow external storage of output data, enhancing service flexibility while streamlining command execution.

Sequence Diagram(s)

sequenceDiagram
    participant User
    participant TestRunner
    participant ConfigManager
    participant OutputManager

    User->>TestRunner: Run Test
    TestRunner->>ConfigManager: Load Configuration
    ConfigManager-->>TestRunner: Return Parameters
    TestRunner->>OutputManager: Generate Load
    OutputManager-->>TestRunner: Store Output
    TestRunner-->>User: Test Results

🐇 In a meadow bright and fair,
New features hop with joyful flair!
With commands so sweet and clear,
Our tests run fast, we have no fear.
Outputs stored, oh what a sight,
Configs managed, all feels right!
Let's celebrate, with leaps and cheer! 🎉

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?

Share

- [X](https://twitter.com/intent/tweet?text=I%20just%20used%20%40coderabbitai%20for%20my%20code%20review%2C%20and%20it%27s%20fantastic%21%20It%27s%20free%20for%20OSS%20and%20offers%20a%20free%20trial%20for%20the%20proprietary%20code.%20Check%20it%20out%3A&url=https%3A//coderabbit.ai) - [Mastodon](https://mastodon.social/share?text=I%20just%20used%20%40coderabbitai%20for%20my%20code%20review%2C%20and%20it%27s%20fantastic%21%20It%27s%20free%20for%20OSS%20and%20offers%20a%20free%20trial%20for%20the%20proprietary%20code.%20Check%20it%20out%3A%20https%3A%2F%2Fcoderabbit.ai) - [Reddit](https://www.reddit.com/submit?title=Great%20tool%20for%20code%20review%20-%20CodeRabbit&text=I%20just%20used%20CodeRabbit%20for%20my%20code%20review%2C%20and%20it%27s%20fantastic%21%20It%27s%20free%20for%20OSS%20and%20offers%20a%20free%20trial%20for%20proprietary%20code.%20Check%20it%20out%3A%20https%3A//coderabbit.ai) - [LinkedIn](https://www.linkedin.com/sharing/share-offsite/?url=https%3A%2F%2Fcoderabbit.ai&mini=true&title=Great%20tool%20for%20code%20review%20-%20CodeRabbit&summary=I%20just%20used%20CodeRabbit%20for%20my%20code%20review%2C%20and%20it%27s%20fantastic%21%20It%27s%20free%20for%20OSS%20and%20offers%20a%20free%20trial%20for%20proprietary%20code)

Tips

### Chat There are 3 ways to chat with [CodeRabbit](https://coderabbit.ai): - Review comments: Directly reply to a review comment made by CodeRabbit. Example: - `I pushed a fix in commit .` - `Generate unit testing code for this file.` - `Open a follow-up GitHub issue for this discussion.` - Files and specific lines of code (under the "Files changed" tab): Tag `@coderabbitai` in a new review comment at the desired location with your query. Examples: - `@coderabbitai generate unit testing code for this file.` - `@coderabbitai modularize this function.` - PR comments: Tag `@coderabbitai` in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples: - `@coderabbitai generate interesting stats about this repository and render them as a table.` - `@coderabbitai show all the console.log statements in this repository.` - `@coderabbitai read src/utils.ts and generate unit testing code.` - `@coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.` - `@coderabbitai help me debug CodeRabbit configuration file.` 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) - `@coderabbitai pause` to pause the reviews on a PR. - `@coderabbitai resume` to resume the paused reviews. - `@coderabbitai review` to trigger an incremental review. This is useful when automatic reviews are disabled for the repository. - `@coderabbitai full review` to do a full review from scratch and review all the files again. - `@coderabbitai summary` to regenerate the summary of the PR. - `@coderabbitai resolve` resolve all the CodeRabbit review comments. - `@coderabbitai configuration` to show the current CodeRabbit configuration for the repository. - `@coderabbitai help` to get help. Additionally, you can add `@coderabbitai ignore` anywhere in the PR description to prevent this PR from being reviewed. ### CodeRabbit Configuration File (`.coderabbit.yaml`) - You can programmatically configure CodeRabbit by adding a `.coderabbit.yaml` file to the root of your repository. - Please see the [configuration documentation](https://docs.coderabbit.ai/guides/configure-coderabbit) for more information. - If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: `# yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json` ### Documentation and Community - Visit our [Documentation](https://coderabbit.ai/docs) for detailed information on how to use CodeRabbit. - Join our [Discord Community](https://discord.com/invite/GsXnASn26c) to get help, request features, and share feedback. - Follow us on [X/Twitter](https://twitter.com/coderabbitai) for updates and announcements.

codecov[bot] commented 4 months ago

Codecov Report

All modified and coverable lines are covered by tests :white_check_mark:

Project coverage is 17.54%. Comparing base (d545b24) to head (192a2a9).

:exclamation: There is a different number of reports uploaded between BASE (d545b24) and HEAD (192a2a9). Click for more details.

HEAD has 12 uploads less than BASE
| Flag | BASE (d545b24) | HEAD (192a2a9) | |------|------|------| ||2|0| |integration_tests|20|10|

Additional details and impacted files

[![Impacted file tree graph](https://app.codecov.io/gh/crypto-org-chain/cronos/pull/1524/graphs/tree.svg?width=650&height=150&src=pr&token=92w0Dz1Coj&utm_medium=referral&utm_source=github&utm_content=comment&utm_campaign=pr+comments&utm_term=crypto-org-chain)](https://app.codecov.io/gh/crypto-org-chain/cronos/pull/1524?src=pr&el=tree&utm_medium=referral&utm_source=github&utm_content=comment&utm_campaign=pr+comments&utm_term=crypto-org-chain) ```diff @@ Coverage Diff @@ ## main #1524 +/- ## =========================================== - Coverage 36.84% 17.54% -19.30% =========================================== Files 117 87 -30 Lines 8124 5273 -2851 =========================================== - Hits 2993 925 -2068 + Misses 4766 4238 -528 + Partials 365 110 -255 ``` [see 53 files with indirect coverage changes](https://app.codecov.io/gh/crypto-org-chain/cronos/pull/1524/indirect-changes?src=pr&el=tree-more&utm_medium=referral&utm_source=github&utm_content=comment&utm_campaign=pr+comments&utm_term=crypto-org-chain)

crypto-org-chain / cronos