Awesome06 opened a new pull request, #27258:
URL: https://github.com/apache/datafusion/pull/27258
## Which issue does this PR close?
Part of #27082.
## Rationale for this change
The `union_fuzz` test in `key_range_bitmap.rs` previously ran as a
standalone `#[test]` using environment variables
(`DATAFUSION_KEY_RANGE_UNION_FUZZ_ITERATIONS` and
`DATAFUSION_KEY_RANGE_UNION_FUZZ_SEED`) without standardized budget controls or
centralized failure reporting.
Migrating this suite to the `FuzzTest` framework introduced in #27048 makes
failures reproducible via seed reporting, connects it to the unified runner in
`datafusion-fuzz`, and aligns it with project-wide fuzz testing conventions.
## What changes are included in this PR?
- **`datafusion-physical-plan`**:
- Expose `KeyRangePart` and `KeyRangeBitmap::union` so `datafusion-fuzz`
can construct partitions and test union behavior.
- Expose `offset(&self)`, `span(&self)`, `shift(&self)`, and `bits(&self)`
getter accessors on `KeyRangeBitmap` for internal invariant checking.
- Remove legacy `union_fuzz` and `run_union_scenario` test functions from
`key_range_bitmap.rs`.
- **`datafusion-fuzz`**:
- Implement `KeyRangeBitmapFuzzer` in `tests/suites/key_range_bitmap.rs`
implementing the `FuzzTest` trait.
- Register `KeyRangeBitmapFuzzer` in `tests/fuzz.rs` and
`tests/suites/mod.rs`.
- **`xtask`**:
- Remove `union_fuzz` from `LEGACY_FUZZ_TESTS` in `ci_steps.rs` and clean
up legacy runner configuration and snapshots.
## What is the testing strategy for this PR?
- Validated `datafusion-physical-plan` unit tests:
- `cargo test -p datafusion-physical-plan --lib --
joins::key_range_bitmap` (all 4 unit tests pass)
- Validated unified fuzz runner:
- `cargo test -p datafusion-fuzz --test fuzz --features extended_tests`
(256 cases pass)
- Validated `xtask` legacy fuzz test verification:
- `cargo test -p datafusion-xtask -- legacy_fuzz_tests_exist`
## Are there any user-facing changes?
No user-facing changes.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
