perf: Optimize NULL handling in array_slice
#62619
rust.yml
on: pull_request
linux build test
1m 49s
build and run with wasm-pack
5m 48s
cargo test (macos-aarch64)
19m 58s
Verify Vendored Code
1m 17s
Check cargo fmt
1m 4s
Verify MSRV (Min Supported Rust Version)
5m 7s
cargo check datafusion-common features
2m 8s
cargo check datafusion-substrait features
4m 10s
cargo check datafusion-proto features
2m 13s
cargo check datafusion features
5m 53s
cargo check datafusion-functions features
2m 39s
cargo test (amd64)
3m 16s
cargo test datafusion-cli (amd64)
1m 53s
cargo examples (amd64)
3m 1s
cargo test doc (amd64)
3m 12s
cargo doc
2m 1s
verify benchmark results (amd64)
4m 28s
Run sqllogictest with Postgres runner
2m 38s
Run sqllogictest in Substrait round-trip mode
2m 31s
clippy
1m 59s
check Cargo.toml formatting
3m 20s
check configs.md and ***_functions.md is up-to-date
2m 16s
check example README is up-to-date
4m 30s
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/
|