Skip to content

1

1 #14

Triggered via pull request May 2, 2026 03:18
Status Failure
Total duration 1m 47s
Artifacts

ci.yaml

on: pull_request
stable / fmt
25s
stable / fmt
stable / check rig-core wasm target
37s
stable / check rig-core wasm target
stable / clippy
1m 16s
stable / clippy
stable / test
1m 42s
stable / test
stable / doc
1m 23s
stable / doc
Fit to window
Zoom out
Zoom in

Annotations

14 errors and 5 warnings
stable / clippy
Clippy has exited with exit code 101
unused import: `ToolServerError`: tests/providers/deepseek/streaming_tools.rs#L9
error: unused import: `ToolServerError` --> tests/providers/deepseek/streaming_tools.rs:9:40 | 9 | use rig::tool::server::{LocalRmcpTool, ToolServerError}; | ^^^^^^^^^^^^^^^
unused import: `ToolServerError`: tests/providers/deepseek/permission_control.rs#L9
error: unused import: `ToolServerError` --> tests/providers/deepseek/permission_control.rs:9:40 | 9 | use rig::tool::server::{LocalRmcpTool, ToolServerError}; | ^^^^^^^^^^^^^^^ | = note: `-D unused-imports` implied by `-D warnings` = help: to override `-D warnings` add `#[allow(unused_imports)]`
impl trait in impl method signature does not match trait method signature: tests/providers/groq/typed_prompt_tools.rs#L50
error: impl trait in impl method signature does not match trait method signature --> tests/providers/groq/typed_prompt_tools.rs:50:69 | 50 | ) -> impl std::future::Future<Output = ToolDefinition> + Send + Sync { | ^^^^ this bound is stronger than that defined on the trait | = note: add `#[allow(refining_impl_trait)]` if it is intended for this to be part of the public API of this crate = note: we are soliciting feedback, see issue #121718 <https://github.com/rust-lang/rust/issues/121718> for more information = note: `-D refining-impl-trait-internal` implied by `-D warnings` = help: to override `-D warnings` add `#[allow(refining_impl_trait_internal)]` = note: the full name for the type has been written to '/home/runner/work/rig/rig/target/debug/deps/groq-9a880cbd7df13015.long-type-10274909034286910856.txt' = note: consider using `--verbose` to print the full type name to the console help: replace the return type so that it matches the trait | 50 - ) -> impl std::future::Future<Output = ToolDefinition> + Send + Sync { 50 + ) -> impl futures::Future<Output = rig::completion::ToolDefinition> + rig::wasm_compat::WasmCompatSend { |
unused import: `ToolServerError`: tests/providers/groq/typed_prompt_tools.rs#L12
error: unused import: `ToolServerError` --> tests/providers/groq/typed_prompt_tools.rs:12:40 | 12 | use rig::tool::server::{LocalRmcpTool, ToolServerError}; | ^^^^^^^^^^^^^^^
unused import: `ToolServerError`: tests/providers/groq/streaming_tools.rs#L9
error: unused import: `ToolServerError` --> tests/providers/groq/streaming_tools.rs:9:40 | 9 | use rig::tool::server::{LocalRmcpTool, ToolServerError}; | ^^^^^^^^^^^^^^^
unused import: `ToolServerError`: tests/providers/groq/permission_control.rs#L9
error: unused import: `ToolServerError` --> tests/providers/groq/permission_control.rs:9:40 | 9 | use rig::tool::server::{LocalRmcpTool, ToolServerError}; | ^^^^^^^^^^^^^^^ | = note: `-D unused-imports` implied by `-D warnings` = help: to override `-D warnings` add `#[allow(unused_imports)]`
stable / test
The process '/home/runner/.cargo/bin/cargo' failed with exit code 101
stable / test: tests/providers/mistral/typed_prompt_tools.rs#L50
impl trait in impl method signature does not match trait method signature
stable / test: tests/providers/mistral/typed_prompt_tools.rs#L12
unused import: `ToolServerError`
stable / test: tests/providers/mistral/permission_control.rs#L9
unused import: `ToolServerError`
stable / test: tests/providers/copilot/typed_prompt_tools.rs#L11
unused import: `ToolServerError`
stable / test: tests/providers/copilot/streaming_tools.rs#L8
unused import: `ToolServerError`
stable / test: tests/providers/copilot/permission_control.rs#L8
unused import: `ToolServerError`
stable / fmt
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4. 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/
stable / check rig-core wasm target
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4. 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/
stable / clippy
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, clechasseur/rs-clippy-check@v3. 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/
stable / doc
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4. 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/
stable / test
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions-rs/cargo@v1, actions/checkout@v4. 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/