Validate Pull Request

feat: add coverage report generation with cargo-llvm-cov #3730

Sign in to view logs

Triggered via pull request March 25, 2026 12:10

dblnz

synchronize #1301

dblnz:rally/1190-generate-coverage-reports

Status Cancelled

Total duration 4m 59s

Artifacts –

ValidatePullRequest.yml

on: pull_request

update-guest-locks / update-guest-locks

spell check with typos

check license headers

Matrix: build-guests

code-checks / linux-checks

code-checks / windows-checks

Matrix: build-test

Waiting for pending jobs

Matrix: fuzzing / fuzz

Waiting for pending jobs

Matrix: run-examples

Waiting for pending jobs

report-ci-status

Annotations

13 errors and 5 warnings

build-guests (release) / build-guests

Canceling since a higher priority waiting request for Validate Pull Request-refs/pull/1301/merge exists

build-guests (release) / build-guests

The operation was canceled.

code-checks / linux-checks

Canceling since a higher priority waiting request for Validate Pull Request-refs/pull/1301/merge exists

code-checks / linux-checks

The operation was canceled.

build-guests (debug) / build-guests

Canceling since a higher priority waiting request for Validate Pull Request-refs/pull/1301/merge exists

build-guests (debug) / build-guests

The operation was canceled.

code-checks / windows-checks

Canceling since a higher priority waiting request for Validate Pull Request-refs/pull/1301/merge exists

code-checks / windows-checks

The operation was canceled.

report-ci-status

Process completed with exit code 1.

Validate Pull Request

Canceling since a higher priority waiting request for Validate Pull Request-refs/pull/1301/merge exists

Validate Pull Request

Canceling since a higher priority waiting request for Validate Pull Request-refs/pull/1301/merge exists

Validate Pull Request

Canceling since a higher priority waiting request for Validate Pull Request-refs/pull/1301/merge exists

Validate Pull Request

Canceling since a higher priority waiting request for Validate Pull Request-refs/pull/1301/merge exists

build-guests (release) / build-guests

Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: extractions/setup-crate@4993624604c307fbca528d28a3c8b60fa5ecc859. 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/

code-checks / linux-checks

Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: extractions/setup-crate@4993624604c307fbca528d28a3c8b60fa5ecc859. 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/

build-guests (debug) / build-guests

Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: extractions/setup-crate@4993624604c307fbca528d28a3c8b60fa5ecc859. 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/

build-guests (debug) / build-guests

Failed to save: "/usr/bin/tar" failed with error: The process '/usr/bin/tar' failed with exit code 1

code-checks / windows-checks

Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: extractions/setup-crate@4993624604c307fbca528d28a3c8b60fa5ecc859. 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/