Skip to content
Rust

using LexOrdering::from_ref fn instead of directly cloning it #54

Sign in to view logs

using LexOrdering::from_ref fn instead of directly cloning it

using LexOrdering::from_ref fn instead of directly cloning it #54

Triggered via push November 2, 2024 20:36
@jatin510jatin510
pushed a9023bf
feature/13220-deprecate-LexOrderingRef-and-LexRequirementRef
Status Failure
Total duration 1h 7m 5s
Artifacts –

rust.yml

on: push
cargo check
5m 11s
cargo check
build with wasm-pack
2m 33s
build with wasm-pack
cargo test (win64)
1h 6m
cargo test (win64)
cargo test (macos)
12m 1s
cargo test (macos)
cargo test (macos-aarch64)
9m 54s
cargo test (macos-aarch64)
Verify Vendored Code
49s
Verify Vendored Code
Check cargo fmt
45s
Check cargo fmt
Verify MSRV (Min Supported Rust Version)
8m 11s
Verify MSRV (Min Supported Rust Version)
cargo test (amd64)
0s
cargo test (amd64)
cargo test datafusion-cli (amd64)
0s
cargo test datafusion-cli (amd64)
cargo examples (amd64)
0s
cargo examples (amd64)
cargo test doc (amd64)
0s
cargo test doc (amd64)
cargo doc
0s
cargo doc
verify benchmark results (amd64)
0s
verify benchmark results (amd64)
Run sqllogictest with Postgres runner
0s
Run sqllogictest with Postgres runner
cargo test pyarrow (amd64)
0s
cargo test pyarrow (amd64)
clippy
0s
clippy
cargo test hash collisions (amd64)
0s
cargo test hash collisions (amd64)
check Cargo.toml formatting
0s
check Cargo.toml formatting
check configs.md and ***_functions.md is up-to-date
0s
check configs.md and ***_functions.md is up-to-date
Fit to window
Zoom out
Zoom in

Annotations

1 error
cargo check
Process completed with exit code 101.