Backport file size fix #109
Triggered via pull request
March 31, 2026 17:03
krinart
Status
Failure
Total duration
1d 0h 0m 3s
Artifacts
–
ci.yml
on: pull_request
lint-toml
9s
validate-workflow-yaml
8s
Python (lint)
0s
Python (test)
1d 0h
Python (wheel build)
3m 40s
Rust (docs)
0s
Check build with minimal dependencies
0s
Rust (lint)
0s
Rust (semver checks)
0s
Rust tests (sanitizer)
0s
Java
0s
C++ build
0s
wasm-integration
2m 43s
Rust tests (miri)
1m 46s
Check generated source files are up to date
3m 35s
Matrix: bench-codspeed
Matrix: build-rust
Matrix: License Check and Audit Check
Matrix: rust-coverage
Matrix: rust-lint-no-default
Matrix: rust-test-other
Annotations
29 errors, 4 warnings, and 4 notices
|
Rust tests (miri)
Process completed with exit code 101.
|
|
Check build with minimal dependencies
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
|
|
Python (test)
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
|
|
Rust build (wasm32 with default features)
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
|
|
Rust (lint, no default, 2/2)
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
|
|
Java
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
|
|
Python (lint)
The job has exceeded the maximum execution time while awaiting a runner for 24h0m0s
|
|
Rust tests (coverage) (tpc-h)
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 #8)
The job has exceeded the maximum execution time while awaiting a runner for 24h0m0s
|
|
Rust tests (coverage) (ffi)
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
|
|
Rust (semver checks)
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
|
|
Benchmark with Codspeed (Shard #2)
The job has exceeded the maximum execution time while awaiting a runner for 24h0m0s
|
|
Rust (lint, no default, 1/2)
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
|
|
Benchmark with Codspeed (Shard #5)
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 tests (sanitizer)
The job has exceeded the maximum execution time while awaiting a runner for 24h0m0s
|
|
C++ build
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 #1)
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 tests (miri)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: arduino/setup-protoc@v3, mozilla-actions/sccache-action@v0.0.9. 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/
|
|
wasm-integration
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: arduino/setup-protoc@v3, 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. 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/
|
|
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: arduino/setup-protoc@v3, mozilla-actions/sccache-action@v0.0.9. 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/
|
|
Python (wheel build)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: arduino/setup-protoc@v3, mlugg/setup-zig@v2, mozilla-actions/sccache-action@v0.0.9. 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/
|
|
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
|
|
sccache stats
0% - 0 hits, 0 misses, 0 errors
|