vibe-prototype: codex solution for join memory counting #35
rust.yml
on: pull_request
linux build test
4m 50s
build and run with wasm-pack
5m 52s
cargo test (macos-aarch64)
6m 6s
Verify Vendored Code
1m 19s
Check cargo fmt
1m 15s
Verify MSRV (Min Supported Rust Version)
5m 59s
cargo check datafusion-common features
1m 56s
cargo check datafusion-substrait features
12m 21s
cargo check datafusion-proto features
5m 28s
cargo check datafusion features
11m 27s
cargo check datafusion-functions features
2m 40s
cargo test (amd64)
12m 27s
cargo test datafusion-cli (amd64)
5m 20s
cargo examples (amd64)
11m 1s
cargo test doc (amd64)
9m 3s
cargo doc
5m 47s
verify benchmark results (amd64)
14m 11s
Run sqllogictest with Postgres runner
6m 55s
Run sqllogictest in Substrait round-trip mode
6m 32s
clippy
2m 43s
check Cargo.toml formatting
3m 20s
check configs.md and ***_functions.md is up-to-date
5m 29s
check example README is up-to-date
5m 18s
Annotations
1 error and 1 warning
|
clippy
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/
|