b5022000c - fix: make PushDownLeafProjections work with unnest #623
rust.yml
on: pull_request
linux build test
7m 8s
build and run with wasm-pack
6m 27s
cargo test (macos-aarch64)
10m 1s
Verify Vendored Code
1m 27s
Check cargo fmt
1m 7s
Verify MSRV (Min Supported Rust Version)
6m 6s
cargo check datafusion-common features
2m 6s
cargo check datafusion-substrait features
12m 41s
cargo check datafusion-proto features
4m 49s
cargo check datafusion features
13m 26s
cargo check datafusion-functions features
2m 53s
cargo test (amd64)
16m 44s
cargo test datafusion-cli (amd64)
5m 22s
cargo examples (amd64)
16m 27s
cargo test doc (amd64)
9m 38s
cargo doc
5m 42s
verify benchmark results (amd64)
12m 50s
Run sqllogictest with Postgres runner
6m 51s
Run sqllogictest in Substrait round-trip mode
7m 31s
clippy
7m 10s
check Cargo.toml formatting
4m 46s
check configs.md and ***_functions.md is up-to-date
6m 0s
check example README is up-to-date
6m 31s
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/
|