CI

Bump quinn-proto from 0.11.13 to 0.11.14 in the cargo group across 1 directory #94

Sign in to view logs

Triggered via pull request March 11, 2026 00:28

dependabot[bot]

opened #32

dependabot/cargo/cargo-6aa8836123

Status Cancelled

Total duration 1d 0h 0m 2s

Artifacts –

ci.yml

on: pull_request

validate-workflow-yaml

Python (wheel build)

Check build with minimal dependencies

Rust (lint, no default)

Public API lock files

Rust tests (sanitizer)

CUDA tests (sanitizer)

CUDA tests (cudf)

SQL logic tests

wasm-integration

Rust tests (miri)

Check generated source files are up to date

Rust publish dry-run

Matrix: bench-codspeed

Matrix: build-rust

Matrix: check-java-publish-build

Matrix: License Check and Audit Check

Matrix: rust-coverage

Matrix: rust-test-other

Annotations

32 errors, 4 warnings, and 3 notices

Python (test)

The job has exceeded the maximum execution time while awaiting a runner for 24h0m0s

Rust build (all-features)

The job has exceeded the maximum execution time while awaiting a runner for 24h0m0s

Rust (docs)

The job has exceeded the maximum execution time while awaiting a runner for 24h0m0s

Public API lock files

The job has exceeded the maximum execution time while awaiting a runner for 24h0m0s

Python (lint)

The job has exceeded the maximum execution time while awaiting a runner for 24h0m0s

Benchmark with Codspeed (Shard #7)

The job has exceeded the maximum execution time while awaiting a runner for 24h0m0s

Check build with minimal dependencies

The job has exceeded the maximum execution time while awaiting a runner for 24h0m0s

Rust (lint)

The job has exceeded the maximum execution time while awaiting a runner for 24h0m0s

Benchmark with Codspeed (Shard #2)

The job has exceeded the maximum execution time while awaiting a runner for 24h0m0s

Rust tests (coverage) (tests)

The job has exceeded the maximum execution time while awaiting a runner for 24h0m0s

The job has exceeded the maximum execution time while awaiting a runner for 24h0m0s

Rust tests (sanitizer)

The job has exceeded the maximum execution time while awaiting a runner for 24h0m0s

Rust build (default features)

The job has exceeded the maximum execution time while awaiting a runner for 24h0m0s

The job has exceeded the maximum execution time while awaiting a runner for 24h0m0s

Benchmark with Codspeed (Shard #6)

The job has exceeded the maximum execution time while awaiting a runner for 24h0m0s

The job has exceeded the maximum execution time while awaiting a runner for 24h0m0s

Rust tests (linux-arm64)

The job has exceeded the maximum execution time while awaiting a runner for 24h0m0s

Rust build (with tokio dispatcher)

The job has exceeded the maximum execution time while awaiting a runner for 24h0m0s

Benchmark with Codspeed (Shard #8)

The job has exceeded the maximum execution time while awaiting a runner for 24h0m0s

Benchmark with Codspeed (Shard #4)

The job has exceeded the maximum execution time while awaiting a runner for 24h0m0s

The job has exceeded the maximum execution time while awaiting a runner for 24h0m0s

Rust (lint, no default)

The job has exceeded the maximum execution time while awaiting a runner for 24h0m0s

Benchmark with Codspeed (Shard #3)

The job has exceeded the maximum execution time while awaiting a runner for 24h0m0s

Rust build (wasm32 with default features)

The job has exceeded the maximum execution time while awaiting a runner for 24h0m0s

CUDA (lint)

The job has exceeded the maximum execution time while awaiting a runner for 24h0m0s

SQL logic tests

The job has exceeded the maximum execution time while awaiting a runner for 24h0m0s

Rust publish dry-run

The job has exceeded the maximum execution time while awaiting a runner for 24h0m0s

Benchmark with Codspeed (Shard #1)

The job has exceeded the maximum execution time while awaiting a runner for 24h0m0s

Rust tests (windows-x64)

The job has exceeded the maximum execution time while awaiting a runner for 24h0m0s

Benchmark with Codspeed (Shard #5)

The job has exceeded the maximum execution time while awaiting a runner for 24h0m0s

CUDA tests (sanitizer)

The job has exceeded the maximum execution time while awaiting a runner for 24h0m0s

CUDA tests (cudf)

The job has exceeded the maximum execution time while awaiting a runner for 24h0m0s

wasm-integration

Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: mozilla-actions/sccache-action@v0.0.9, wasmerio/setup-wasmer@v3.1. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/

Rust tests (miri)

Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: mozilla-actions/sccache-action@v0.0.9. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/

Check generated source files are up to date

Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: mozilla-actions/sccache-action@v0.0.9. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/

Python (wheel build)

Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: mlugg/setup-zig@v2, Swatinem/rust-cache@v2. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/

sccache stats

0% - 0 hits, 0 misses, 0 errors

sccache stats

0% - 0 hits, 0 misses, 0 errors

sccache stats

0% - 0 hits, 0 misses, 0 errors