refactor(physical-plan): extract make_group_column factory + eager init at try_new + tighten Time variants #67971
zhuqi-lucasrust.yml
on: pull_request
linux build test
5m 43s
build and run with wasm-pack
6m 33s
cargo test (macos-aarch64)
7m 18s
Verify Vendored Code
2m 19s
Check cargo fmt
1m 10s
Verify MSRV (Min Supported Rust Version)
5m 46s
cargo check datafusion-common features
1m 58s
cargo check datafusion-substrait features
12m 5s
cargo check datafusion-proto features
5m 14s
cargo check datafusion features
12m 11s
cargo check datafusion-functions features
2m 39s
cargo test (amd64)
13m 10s
cargo test datafusion-cli (amd64)
5m 21s
cargo examples (amd64)
15m 11s
cargo test doc (amd64)
10m 21s
cargo doc
5m 22s
verify benchmark results (amd64)
14m 40s
Run sqllogictest with Postgres runner
7m 20s
Run sqllogictest in Substrait round-trip mode
7m 43s
clippy
6m 17s
check Cargo.toml formatting
4m 32s
check configs.md and ***_functions.md is up-to-date
6m 14s
check example README is up-to-date
7m 3s
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/
|