proto: serialize dynamic filters on Sort, Aggregate, HashJoin plan no… #183
rust.yml
on: push
linux build test
7m 51s
build and run with wasm-pack
6m 0s
cargo test (macos-aarch64)
6m 50s
Verify Vendored Code
1m 8s
Check cargo fmt
1m 9s
Verify MSRV (Min Supported Rust Version)
6m 7s
cargo check datafusion-common features
2m 5s
cargo check datafusion-substrait features
12m 6s
cargo check datafusion-proto features
4m 29s
cargo check datafusion features
11m 18s
cargo check datafusion-functions features
2m 41s
cargo test (amd64)
15m 55s
cargo test datafusion-cli (amd64)
5m 10s
cargo examples (amd64)
17m 1s
cargo test doc (amd64)
8m 48s
cargo doc
5m 38s
verify benchmark results (amd64)
13m 36s
Run sqllogictest with Postgres runner
7m 4s
Run sqllogictest in Substrait round-trip mode
7m 3s
clippy
7m 46s
check Cargo.toml formatting
3m 26s
check configs.md and ***_functions.md is up-to-date
6m 9s
check example README is up-to-date
5m 8s
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 2nd, 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/
|