Closed WenyXu closed 3 months ago
[!NOTE]
Reviews paused
Use the following commands to manage reviews:
@coderabbitai resume
to resume automatic reviews.@coderabbitai review
to trigger a single review.
This update introduces a new fuzz testing binary for assessing failover scenarios in a distributed system. The functionality includes operations like creating and querying tables, simulating failures, and maintaining data integrity. Additionally, improvements are made to log messages in an existing fuzz test.
File Path | Summary |
---|---|
tests-fuzz/Cargo.toml |
Added new binary entry fuzz_failover_metric_regions . |
tests-fuzz/targets/failover/fuzz_failover_metric_regions.rs |
Added new functionality for fuzz testing failover scenarios. |
tests-fuzz/targets/failover/fuzz_failover_mito_regions.rs |
Updated log messages to improve clarity. |
sequenceDiagram
participant Tester
participant FuzzContext
participant PhysicalTable
participant LogicalTable
Tester->>FuzzContext: Create FuzzContext
FuzzContext->>PhysicalTable: create_physical_table()
PhysicalTable->>FuzzContext: return TableContextRef
FuzzContext->>LogicalTable: create_logical_table(TableContextRef)
LogicalTable->>FuzzContext: return LogicalTableContextRef
Tester->>FuzzContext: insert_values()
FuzzContext->>LogicalTable: Generate & Insert Data Rows
LogicalTable->>FuzzContext: return InsertResult
Tester->>FuzzContext: execute_failover()
FuzzContext->>Tester: Validate & return Result
GreptimeTeam/greptimedb#4234
fuzz_failover_mito_regions
.GreptimeTeam/greptimedb#4245
fuzz_insert_logical_table
.In data's dance with graceful twirl, Fuzz tests march and metrics swirl. Tables build, both great and small, Integrity proves against the fall. Logs now clearer, errors find, Apps grow stronger, chaos tamed in kind.
✨🐇🌐✨
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?
@coderabbitai pause
Attention: Patch coverage is 0%
with 4 lines
in your changes missing coverage. Please review.
Project coverage is 84.69%. Comparing base (
76fac35
) to head (bdc2b3b
). Report is 11 commits behind head on main.
I hereby agree to the terms of the GreptimeDB CLA.
Refer to a related PR or issue link (optional)
What's changed and what's your intention?
Add naive failover test for metric table
Checklist
Summary by CodeRabbit