Skip to content

Add has_tool for ToolManager #2436

Add has_tool for ToolManager

Add has_tool for ToolManager #2436

Triggered via pull request August 12, 2025 05:44
Status Success
Total duration 2m 22s
Artifacts

pull-request-checks.yml

on: pull_request
checks  /  pre-commit
26s
checks / pre-commit
checks  /  readme-snippets
13s
checks / readme-snippets
Matrix: checks / test
Fit to window
Zoom out
Zoom in

Annotations

16 warnings and 4 notices
checks / test (3.12, ubuntu-latest)
Failed to save: <h2>Our services aren't available right now</h2><p>We're working to restore all services as soon as possible. Please check back soon.</p>06dSaaAAAAAAOIHQRbrFYTKdck1acR4qZQkwyQUEyMDMwMTA5MDM1AEVkZ2U=
checks / test (3.12, ubuntu-latest)
Failed to restore: Cache service responded with 400
checks / test (3.11, ubuntu-latest)
Failed to save: <h2>Our services aren't available right now</h2><p>We're working to restore all services as soon as possible. Please check back soon.</p>06tSaaAAAAAAFlE02TGFtRbQcw/FPrh26Q0gxRURHRTExMTQARWRnZQ==
checks / test (3.11, ubuntu-latest)
Failed to restore: Cache service responded with 400
checks / test (3.13, ubuntu-latest)
Failed to save: <h2>Our services aren't available right now</h2><p>We're working to restore all services as soon as possible. Please check back soon.</p>07tSaaAAAAABiLB7zmnGXTrJDHh6pVhy0QkwyQUEyMDMwMTA3MDM1AEVkZ2U=
checks / test (3.13, ubuntu-latest)
Failed to restore: Cache service responded with 400
checks / test (3.10, ubuntu-latest)
Failed to save: <h2>Our services aren't available right now</h2><p>We're working to restore all services as soon as possible. Please check back soon.</p>07dSaaAAAAADbgTcND/ovTLnM6gEPkRZVUEFPRURHRTA2MTUARWRnZQ==
checks / test (3.10, ubuntu-latest)
Failed to restore: Cache service responded with 400
checks / test (3.10, windows-latest)
Failed to save: <h2>Our services aren't available right now</h2><p>We're working to restore all services as soon as possible. Please check back soon.</p>0KtWaaAAAAAAkEbmnPYM3R6OuS7JTtRcYUEFPRURHRTA1MTQARWRnZQ==
checks / test (3.10, windows-latest)
Failed to restore: Cache service responded with 400
checks / test (3.11, windows-latest)
Failed to save: <h2>Our services aren't available right now</h2><p>We're working to restore all services as soon as possible. Please check back soon.</p>0LtWaaAAAAADTut6FihaJRLvevOXCnvp/QkwyQUEyMDMwMTA2MDUzAEVkZ2U=
checks / test (3.11, windows-latest)
Failed to restore: Cache service responded with 400
checks / test (3.13, windows-latest)
Failed to save: <h2>Our services aren't available right now</h2><p>We're working to restore all services as soon as possible. Please check back soon.</p>0NNWaaAAAAACdf8mkNqxZT5RFCkVEXRy9UEhYMzFFREdFMDUyMQBFZGdl
checks / test (3.13, windows-latest)
Failed to restore: Cache service responded with 400
checks / test (3.12, windows-latest)
Failed to save: <h2>Our services aren't available right now</h2><p>We're working to restore all services as soon as possible. Please check back soon.</p>0N9WaaAAAAABE3EddjJKOTr5CYXLdMZnbQ0gxRURHRTE4MDgARWRnZQ==
checks / test (3.12, windows-latest)
Failed to restore: Cache service responded with 400
checks / test (3.10, windows-latest)
The windows-latest label will migrate from Windows Server 2022 to Windows Server 2025 beginning September 2, 2025. For more information see https://github.com/actions/runner-images/issues/12677
checks / test (3.11, windows-latest)
The windows-latest label will migrate from Windows Server 2022 to Windows Server 2025 beginning September 2, 2025. For more information see https://github.com/actions/runner-images/issues/12677
checks / test (3.13, windows-latest)
The windows-latest label will migrate from Windows Server 2022 to Windows Server 2025 beginning September 2, 2025. For more information see https://github.com/actions/runner-images/issues/12677
checks / test (3.12, windows-latest)
The windows-latest label will migrate from Windows Server 2022 to Windows Server 2025 beginning September 2, 2025. For more information see https://github.com/actions/runner-images/issues/12677