Add MERGE INTO types to datafusion-expr #68151
alambrust.yml
on: pull_request
linux build test
5m 35s
build and run with wasm-pack
6m 51s
cargo test (macos-aarch64)
8m 29s
Verify Vendored Code
1m 6s
Check cargo fmt
57s
Verify MSRV (Min Supported Rust Version)
5m 48s
cargo check datafusion-common features
2m 0s
cargo check datafusion-substrait features
14m 5s
cargo check datafusion-proto features
5m 19s
cargo check datafusion features
11m 37s
cargo check datafusion-functions features
2m 24s
cargo test (amd64)
14m 28s
cargo test datafusion-cli (amd64)
5m 35s
cargo examples (amd64)
14m 32s
cargo test doc (amd64)
9m 47s
cargo doc
5m 58s
verify benchmark results (amd64)
15m 44s
Run sqllogictest with Postgres runner
7m 43s
Run sqllogictest in Substrait round-trip mode
9m 7s
clippy
6m 45s
check Cargo.toml formatting
3m 44s
check configs.md and ***_functions.md is up-to-date
5m 28s
check example README is up-to-date
6m 39s
Annotations
1 error and 1 warning
|
cargo test (amd64)
Process completed with exit code 101.
|
|
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/
|