Rust

Improve parsing for associated type usage and add better errors for unsupported patterns #6260

Sign in to view logs

Triggered via pull request March 19, 2026 20:15

mootz12

synchronize #1780

associated-type-errors

Status Cancelled

Total duration 5m 16s

Artifacts –

rust.yml

on: pull_request

check-git-rev-deps

expand-test-wasms

Matrix: cargo-deny

Matrix: publish-dry-run

Waiting for pending jobs

Matrix: build

Matrix: test

Annotations

23 errors and 8 warnings

build (latest, ubuntu-latest, x86_64-unknown-linux-gnu)

Canceling since a higher priority waiting request for Rust-refs/pull/1780/merge-{{ github.event_name }} exists

build (latest, ubuntu-latest, x86_64-unknown-linux-gnu)

A task was canceled.

cargo-deny (advisories)

Canceling since a higher priority waiting request for Rust-refs/pull/1780/merge-{{ github.event_name }} exists

cargo-deny (advisories)

The operation was canceled.

expand-test-wasms

Canceling since a higher priority waiting request for Rust-refs/pull/1780/merge-{{ github.event_name }} exists

expand-test-wasms

The operation was canceled.

migration-docs

Canceling since a higher priority waiting request for Rust-refs/pull/1780/merge-{{ github.event_name }} exists

migration-docs

The operation was canceled.

Canceling since a higher priority waiting request for Rust-refs/pull/1780/merge-{{ github.event_name }} exists

The operation was canceled.

Canceling since a higher priority waiting request for Rust-refs/pull/1780/merge-{{ github.event_name }} exists

The operation was canceled.

Canceling since a higher priority waiting request for Rust-refs/pull/1780/merge-{{ github.event_name }} exists

The operation was canceled.

Canceling since a higher priority waiting request for Rust-refs/pull/1780/merge-{{ github.event_name }} exists

The operation was canceled.

semver-checks

Canceling since a higher priority waiting request for Rust-refs/pull/1780/merge-{{ github.event_name }} exists

semver-checks

The operation was canceled.

cargo-deny (bans licenses sources)

Canceling since a higher priority waiting request for Rust-refs/pull/1780/merge-{{ github.event_name }} exists

cargo-deny (bans licenses sources)

The operation was canceled.

build (msrv, ubuntu-latest, x86_64-unknown-linux-gnu)

Canceling since a higher priority waiting request for Rust-refs/pull/1780/merge-{{ github.event_name }} exists

Process completed with exit code 1.

Canceling since a higher priority waiting request for Rust-refs/pull/1780/merge-{{ github.event_name }} exists

check-git-rev-deps

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

expand-test-wasms

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

migration-docs

Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, actions/checkout@v3. 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/

Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, actions/checkout@v3. 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/

Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, actions/checkout@v3. 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/

Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, actions/checkout@v3. 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/

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

semver-checks

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