perf: Optimize semi-, anti-join implementation using existence probes #68154
rust.yml
on: pull_request
linux build test
5m 53s
build and run with wasm-pack
5m 52s
cargo test (macos-aarch64)
7m 12s
Verify Vendored Code
2m 14s
Check cargo fmt
1m 19s
Verify MSRV (Min Supported Rust Version)
6m 0s
cargo check datafusion-common features
2m 36s
cargo check datafusion-substrait features
12m 55s
cargo check datafusion-proto features
5m 8s
cargo check datafusion features
12m 6s
cargo check datafusion-functions features
2m 41s
cargo test (amd64)
14m 9s
cargo test datafusion-cli (amd64)
5m 26s
cargo examples (amd64)
13m 45s
cargo test doc (amd64)
8m 51s
cargo doc
4m 9s
verify benchmark results (amd64)
12m 54s
Run sqllogictest with Postgres runner
6m 33s
Run sqllogictest in Substrait round-trip mode
6m 55s
clippy
6m 3s
check Cargo.toml formatting
3m 34s
check configs.md and ***_functions.md is up-to-date
6m 24s
check example README is up-to-date
5m 29s
Annotations
1 error and 1 warning
|
cargo doc
Process completed with exit code 101.
|
|
cargo test (macos-aarch64)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: Swatinem/rust-cache@f13886b937689c021905a6b90929199931d60db1. Actions will be forced to run with Node.js 24 by default starting June 16th, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|