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