Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

benchmark q17 produces incorrect result #4026

Closed
andygrove opened this issue Oct 29, 2022 · 0 comments · Fixed by #4044
Closed

benchmark q17 produces incorrect result #4026

andygrove opened this issue Oct 29, 2022 · 0 comments · Fixed by #4044
Labels
bug Something isn't working
Milestone

Comments

@andygrove
Copy link
Member

Describe the bug

running 1 test
Running benchmarks with the following options: DataFusionBenchmarkOpt { query: 17, debug: false, iterations: 1, partitions: 2, batch_size: 8192, path: "/home/andy/git/apache/arrow-datafusion/benchmarks/data", file_format: "tbl", mem_table: false, output_path: None, disable_statistics: false }
Query 17 iteration 0 took 10768.3 ms and returned 1 rows
Query 17 avg time: 10768.25 ms
expected_fields: [Field { name: "avg_yearly", data_type: Decimal128(38, 2), nullable: true, dict_id: 0, dict_is_ordered: false, metadata: None }]
transformed_fields: [Field { name: "avg_yearly", data_type: Decimal128(38, 2), nullable: true, dict_id: 0, dict_is_ordered: false, metadata: None }]
thread 'tests::verify_q17' panicked at 'assertion failed: `(left == right)`
  left: `["348406.02"]`,
 right: `["NULL"]`', benchmarks/src/bin/tpch.rs:1008:13
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace
test tests::verify_q17 ... FAILED

To Reproduce
Steps to reproduce the behavior:

Expected behavior
A clear and concise description of what you expected to happen.

Additional context
Add any other context about the problem here.

@andygrove andygrove added the bug Something isn't working label Oct 29, 2022
@andygrove andygrove added this to the 14.0.0 milestone Oct 29, 2022
@andygrove andygrove changed the title benchmarkl q17 produces incorrect result benchmark q17 produces incorrect result Oct 30, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
1 participant