2010YOUY01 opened a new pull request, #27604: URL: https://github.com/apache/datafusion/pull/27604
## Which issue does this PR close? Part of #27082. Stack 1/3: memory accounting → timestamp arithmetic → stream merge. These three refactors are independent. They are stacked only to avoid merge conflicts in the shared fuzz registration and dependency files. ## Rationale for this change Move the existing randomized memory-accounting check into the shared fuzz runner to explore more operation sequences and report seeds for replay. For example, two overlapping array slices should count their shared buffer once; removing one slice must keep that buffer counted while the other remains held. ## What changes are included in this PR? Replace the standalone unit test with `RecordBatchMemoryFuzzer`. Each case performs 300 random count/uncount operations and compares the incremental tracker with a fresh recount after every operation. Reading order: 1. `datafusion/fuzz/tests/suites/memory.rs::RecordBatchMemoryFuzzer`: shared-buffer fixtures and accounting invariant. 2. `datafusion/fuzz/tests/fuzz.rs::record_batch_memory_tracker`: one-second campaign. 3. `datafusion/common/src/utils/memory.rs`: removal of the migrated test. ## What is the testing strategy for this PR? After rebasing the three-commit stack onto main (`a56c519bc`), all three migrated suites passed together: ```bash CARGO_CACHE_RUSTC_INFO=0 cargo test --locked --profile ci -p datafusion-fuzz --features extended_tests --test fuzz -- --skip spill_pool_scenario --skip key_range_bitmap_union --skip lru_queue --skip sort_topk --nocapture --test-threads=1 ``` ```text Fuzz suite merge: 20818 cases, 2975 datasets, 4.000042s Fuzz suite record_batch_memory_tracker: 2535 cases, 26 datasets, 1.000325083s Fuzz suite timestamp_arithmetic: 30459 cases, 31 datasets, 1.000006625s test result: ok. 3 passed; 0 failed; 0 ignored; 0 measured; 4 filtered out; finished in 6.00s ``` `cargo fmt --all -- --check` and `git diff --check upstream/main..HEAD` also passed. ## Are there any user-facing changes? No. -- 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]
