Skip to content

Fastmcp logging progress example #2453

Fastmcp logging progress example

Fastmcp logging progress example #2453

Triggered via pull request August 13, 2025 20:53
Status Success
Total duration 2m 20s
Artifacts

pull-request-checks.yml

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

Annotations

1 error, 15 warnings, and 4 notices
checks / test (3.10, windows-latest)
Process completed with exit code 1.
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>0afucaAAAAAAVDJ33l6MkRqilICbtehIsQkwyQUEyMDMwMTA2MDI1AEVkZ2U=
checks / test (3.11, ubuntu-latest)
Failed to restore: Cache service responded with 400
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>0afucaAAAAACtigJaWe7DQrJ8Q4e5Y64WQlkzRURHRTAyMTUARWRnZQ==
checks / test (3.12, 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>0avucaAAAAACEv3jCWwQkRqM2UzbhVshhQkwyQUEyMDMwMTA2MDQ5AEVkZ2U=
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>0bfucaAAAAACdi1Tco3jzTJtatOK3uANdUEhYMzFFREdFMDUxNwBFZGdl
checks / test (3.10, ubuntu-latest)
Failed to restore: Cache service responded with 400
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>0r/ucaAAAAADeuP5CpoRoSLny5/+ZuRtzQkwyQUEyMDMwMTA4MDUzAEVkZ2U=
checks / test (3.11, 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>0sfucaAAAAAALkeiILM8WT4LtT0xZVyCjQkwyQUEyMDMwMTA3MDM5AEVkZ2U=
checks / test (3.12, 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>0tfucaAAAAAAt7KysR0+RRq0/98ryPZRJQkwyQUEyMDMwMTA3MDAzAEVkZ2U=
checks / test (3.13, 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.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
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