robtandy opened a new pull request, #74: URL: https://github.com/apache/datafusion-ray/pull/74
### Working CI tpch validation tests Should fix #11, and maybe eliminates the need for #33. Now, when the `main` branch is pushed to, or a PR is opened against main, CI will run that will validate TPCH results at scale factor 1. This test will let us ensure that we do not stray from correct query execution as we iterate. This test also executes over a matrix of python versions, `3.10, 3.11, 3.12` and ray versions `2.40, 2.41, 2.42.1, 2.43`, to ensure that combinations of these pass. A status indicator of whether the main branch passes tests is shown in the Readme. Example execution of these tests can be seen in the fork: https://github.com/robtandy/datafusion-ray/actions/runs/13638548828 ### `uv` in addition to `pip` - Using `uv` for CI makes sense as its so much faster. Turns out its good for local dev too. I updated `docs/contributing.md` to document the workflow borrowing much from the `datafusion-python` readme and its workflow. ### Other Small changes - rename `--partitions-per-worker` to `--partitions-per-processor` in `tpcbench.py` - return an error return code if one or more queries do not validate in `tpcbench.py` -- 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: github-unsubscr...@datafusion.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org --------------------------------------------------------------------- To unsubscribe, e-mail: github-unsubscr...@datafusion.apache.org For additional commands, e-mail: github-h...@datafusion.apache.org
