refactor: extract sort pushdown logic from FileScanConfig into separate module #62563
rust.yml
on: pull_request
linux build test
2m 26s
build and run with wasm-pack
5m 37s
cargo test (macos-aarch64)
17m 34s
Verify Vendored Code
1m 24s
Check cargo fmt
1m 17s
Verify MSRV (Min Supported Rust Version)
5m 20s
cargo check datafusion-common features
2m 3s
cargo check datafusion-substrait features
4m 8s
cargo check datafusion-proto features
2m 11s
cargo check datafusion features
5m 50s
cargo check datafusion-functions features
2m 46s
cargo test (amd64)
4m 34s
cargo test datafusion-cli (amd64)
3m 12s
cargo examples (amd64)
4m 13s
cargo test doc (amd64)
4m 30s
cargo doc
1m 58s
verify benchmark results (amd64)
5m 37s
Run sqllogictest with Postgres runner
3m 37s
Run sqllogictest in Substrait round-trip mode
3m 44s
clippy
3m 16s
check Cargo.toml formatting
4m 47s
check configs.md and ***_functions.md is up-to-date
3m 37s
check example README is up-to-date
6m 15s
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/
|