mirror of https://github.com/GreptimeTeam/greptimedb.git synced 2025-12-26 08:00:01 +00:00

Files

niebayes d33435fa84 feat: introduce wal benchmarker (#3446 )

* feat: introduce wal benchmarker

* chore: add log store metrics

* chore: add some comments to wal benchmarker

* fix: ci

* chore: add more metrics for kafka logstore

* chore: add more timers for kafka logstore

* chore: add more configs

* chore: move humantime to common dependencies

* refactor: refactor wal benchmarker

* fix: apply suggestions from code review

* doc: add a simple README for wal benchmarker

* fix: Cargo.toml

* fix: clippy

* chore: rename wal.rs to wal_bench.rs

* fix: compile

2024-04-03 03:16:05 +00:00

src

feat(fuzz): add alter table target (#3503 )

2024-03-13 14:11:47 +00:00

targets

feat(fuzz): add alter table target (#3503 )

2024-03-13 14:11:47 +00:00

Cargo.toml

feat: introduce wal benchmarker (#3446 )

2024-04-03 03:16:05 +00:00

README.md

test: add fuzz test for create table (#3441 )

2024-03-07 06:51:19 +00:00

README.md

Fuzz Test for GreptimeDB

Setup

Install the fuzz cli first.

cargo install cargo-fuzz

Start GreptimeDB
Copy the .env.example, which is at project root, to .env and change the values on need.

Run

List all fuzz targets

cargo fuzz list --fuzz-dir tests-fuzz

Run a fuzz target.

cargo fuzz run fuzz_create_table --fuzz-dir tests-fuzz

Crash Reproduction

If you want to reproduce a crash, you first need to obtain the Base64 encoded code, which usually appears at the end of a crash report, and store it in a file.

Alternatively, if you already have the crash file, you can skip this step.

echo "Base64" > .crash

Print the std::fmt::Debug output for an input.

cargo fuzz fmt fuzz_target .crash --fuzz-dir tests-fuzz

Rerun the fuzz test with the input.

cargo fuzz run fuzz_target .crash --fuzz-dir tests-fuzz

For more details, visit cargo fuzz or run the command cargo fuzz --help.