refactor: make scalar distance u64 and overflow aware #68114
rust.yml
on: pull_request
linux build test
6m 10s
build and run with wasm-pack
6m 23s
cargo test (macos-aarch64)
7m 24s
Verify Vendored Code
1m 20s
Check cargo fmt
1m 15s
Verify MSRV (Min Supported Rust Version)
5m 30s
cargo check datafusion-common features
1m 49s
cargo check datafusion-substrait features
12m 6s
cargo check datafusion-proto features
5m 13s
cargo check datafusion features
12m 13s
cargo check datafusion-functions features
2m 41s
cargo test (amd64)
14m 35s
cargo test datafusion-cli (amd64)
6m 38s
cargo examples (amd64)
14m 52s
cargo test doc (amd64)
9m 1s
cargo doc
5m 38s
verify benchmark results (amd64)
15m 53s
Run sqllogictest with Postgres runner
7m 1s
Run sqllogictest in Substrait round-trip mode
9m 19s
clippy
7m 56s
check Cargo.toml formatting
4m 57s
check configs.md and ***_functions.md is up-to-date
5m 58s
check example README is up-to-date
6m 54s
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/
|