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

Integration tests fail #360

Closed
Tracked by #273
andygrove opened this issue Oct 16, 2022 · 0 comments · Fixed by #367
Closed
Tracked by #273

Integration tests fail #360

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

Comments

@andygrove
Copy link
Member

Describe the bug

Starting arrow-ballista_etcd_1 ... done
Starting arrow-ballista_ballista-scheduler_1 ... done
Starting arrow-ballista_ballista-executor_1  ... done
+ for query in 1 3 5 6 7 10 12 13
+ /root/tpch benchmark ballista --host ballista-scheduler --port 50050 --query 1 --path /data --format tbl --iterations 1 --debug
Running benchmarks with the following options: BallistaBenchmarkOpt { query: 1, debug: true, iterations: 1, batch_size: 8192, path: "/data", file_format: "tbl", partitions: 2, host: Some("ballista-scheduler"), port: Some(50050), output_path: None }
[2022-10-16T14:50:21Z INFO  ballista::context] Connecting to Ballista scheduler at http://ballista-scheduler:50050
Error: Execution("DataFusionError(Execution(\"tonic::transport::Error(Transport, hyper::Error(Connect, ConnectError(\\\"tcp connect error\\\", Os { code: 111, kind: ConnectionRefused, message: \\\"Connection refused\\\" })))\"))")

To Reproduce

./dev/integration-tests.sh

Expected behavior
Should run queries successfully

Additional context
None

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
Development

Successfully merging a pull request may close this issue.

1 participant