fix: preserve timestamp precision when coercing mixed time units #67643
rust.yml
on: pull_request
linux build test
4m 30s
build and run with wasm-pack
6m 20s
cargo test (macos-aarch64)
4m 58s
Verify Vendored Code
1m 11s
Check cargo fmt
1m 47s
Verify MSRV (Min Supported Rust Version)
5m 55s
cargo check datafusion-common features
2m 5s
cargo check datafusion-substrait features
11m 52s
cargo check datafusion-proto features
4m 38s
cargo check datafusion features
11m 39s
cargo check datafusion-functions features
2m 42s
cargo test (amd64)
13m 6s
cargo test datafusion-cli (amd64)
5m 23s
cargo examples (amd64)
10m 40s
cargo test doc (amd64)
9m 28s
cargo doc
5m 44s
verify benchmark results (amd64)
14m 5s
Run sqllogictest with Postgres runner
7m 59s
Run sqllogictest in Substrait round-trip mode
7m 24s
clippy
5m 41s
check Cargo.toml formatting
3m 5s
check configs.md and ***_functions.md is up-to-date
5m 55s
check example README is up-to-date
5m 25s
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/
|