fix: bound RepartitionExec channel memory with a byte-budget gate #65263
rust.yml
on: pull_request
linux build test
3m 56s
build and run with wasm-pack
5m 25s
cargo test (macos-aarch64)
3m 54s
Verify Vendored Code
1m 29s
Check cargo fmt
1m 27s
Verify MSRV (Min Supported Rust Version)
5m 21s
cargo check datafusion-common features
2m 9s
cargo check datafusion-substrait features
10m 37s
cargo check datafusion-proto features
4m 41s
cargo check datafusion features
10m 17s
cargo check datafusion-functions features
3m 3s
cargo test (amd64)
10m 13s
cargo test datafusion-cli (amd64)
4m 14s
cargo examples (amd64)
9m 3s
cargo test doc (amd64)
7m 18s
cargo doc
5m 41s
verify benchmark results (amd64)
12m 14s
Run sqllogictest with Postgres runner
6m 15s
Run sqllogictest in Substrait round-trip mode
5m 2s
clippy
4m 49s
check Cargo.toml formatting
3m 23s
check configs.md and ***_functions.md is up-to-date
5m 16s
check example README is up-to-date
4m 44s
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/
|