fix: Correct computation of selectivity for multi-key joins (#22725) #184
rust.yml
on: push
linux build test
6m 7s
build and run with wasm-pack
5m 42s
cargo test (macos-aarch64)
9m 43s
Verify Vendored Code
1m 30s
Check cargo fmt
55s
Verify MSRV (Min Supported Rust Version)
5m 44s
cargo check datafusion-common features
2m 9s
cargo check datafusion-substrait features
11m 57s
cargo check datafusion-proto features
4m 52s
cargo check datafusion features
11m 39s
cargo check datafusion-functions features
2m 37s
cargo test (amd64)
16m 38s
cargo test datafusion-cli (amd64)
6m 33s
cargo examples (amd64)
18m 2s
cargo test doc (amd64)
10m 3s
cargo doc
5m 26s
verify benchmark results (amd64)
18m 3s
Run sqllogictest with Postgres runner
8m 15s
Run sqllogictest in Substrait round-trip mode
8m 0s
clippy
10m 2s
check Cargo.toml formatting
4m 38s
check configs.md and ***_functions.md is up-to-date
7m 18s
check example README is up-to-date
6m 22s
Annotations
1 warning
|
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/
|