2010YOUY01 commented on issue #16452:
URL: https://github.com/apache/datafusion/issues/16452#issuecomment-2987099050
Thanks for reporting!
This failure should be reproducable by
```rust
/// Reproduce the bug with specific seeds from the failing test case
#[tokio::test]
async fn test_reproduce_sort_query_bug() {
// Seeds from the failing test case
let init_seed = 10313160656544581998u64;
let query_seed = 15004039071976572201u64;
let config_seed_1 = 11807432710583113300u64;
let config_seed_2 = 759937414670321802u64;
// Use a fixed seed to replicate the original behavior more closely
let random_seed = 1u64; // Use a fixed seed to ensure consistent
behavior
println!("Creating test generator with same config as original
runner...");
let test_generator = SortFuzzerTestGenerator::new(
2000,
3,
"sort_fuzz_table".to_string(),
get_supported_types_columns(random_seed),
false,
random_seed,
);
// Create a fuzzer with the same configuration as the original
let mut fuzzer = SortQueryFuzzer::new(random_seed)
.with_max_rounds(Some(1))
.with_queries_per_round(2)
.with_config_variations_per_query(2)
.with_test_generator(test_generator);
// Try to run and catch any errors
match fuzzer.run().await {
Ok(_) => println!("Fuzzer completed successfully - bug may have
been fixed"),
Err(e) => {
println!("Fuzzer failed with error: {}", e);
panic!("Reproduced the bug: {}", e);
}
}
}
```
However, I’ve run it several times and it always passes.
This could be either:
- a bug in the fuzzer, or
- a heisenbug that depends on Tokio’s scheduling order.
--
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]
