Skip to content

fuzz_tests suite sometimes results in corrupted databases that are not reproducible by running an individual test #3812

@jussisaurio

Description

@jussisaurio

For example:

test fuzz_tests::index_scan_compound_key_fuzz ... FAILED

thread 'fuzz_tests::index_scan_compound_key_fuzz' panicked at tests/integration/common.rs:214:39:
called `Result::unwrap()` on an `Err` value: SqliteFailure(Error { code: DatabaseCorrupt, extended_code: 11 }, Some("database disk image is malformed"))

This test fails on a database created with rusqlite, when inserting rows into it using rusqlite. another example of non-reproducible failures in the suite: https://github.com/tursodatabase/turso/actions/runs/18729339809/job/53422145981?pr=3809

I have been able to (sometimes) reproduce the index_scan_compound_key_fuzz failure, but only when running the entire test suite cargo test --test fuzz_tests

Metadata

Metadata

Assignees

No one assigned

    Labels

    Type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions