Fix: avoid uncessary retries in OAuth authenticated requests #2503
pull-request-checks.yml
on: pull_request
checks
/
pre-commit
15s
checks
/
readme-snippets
13s
Matrix: checks / test
Annotations
17 errors, 16 warnings, and 8 notices
checks / pre-commit
Process completed with exit code 1.
|
checks / test (3.12, lowest-direct, ubuntu-latest)
Process completed with exit code 1.
|
checks / test (3.13, lowest-direct, ubuntu-latest)
Process completed with exit code 1.
|
checks / test (3.11, lowest-direct, ubuntu-latest)
Process completed with exit code 1.
|
checks / test (3.10, highest, ubuntu-latest)
Process completed with exit code 1.
|
checks / test (3.11, highest, ubuntu-latest)
Process completed with exit code 1.
|
checks / test (3.12, highest, ubuntu-latest)
Process completed with exit code 1.
|
checks / test (3.10, lowest-direct, ubuntu-latest)
Process completed with exit code 1.
|
checks / test (3.13, highest, ubuntu-latest)
Process completed with exit code 1.
|
checks / test (3.10, highest, windows-latest)
Process completed with exit code 1.
|
checks / test (3.10, lowest-direct, windows-latest)
Process completed with exit code 1.
|
checks / test (3.11, lowest-direct, windows-latest)
Process completed with exit code 1.
|
checks / test (3.12, lowest-direct, windows-latest)
Process completed with exit code 1.
|
checks / test (3.11, highest, windows-latest)
Process completed with exit code 1.
|
checks / test (3.12, highest, windows-latest)
Process completed with exit code 1.
|
checks / test (3.13, highest, windows-latest)
Process completed with exit code 1.
|
checks / test (3.13, lowest-direct, windows-latest)
Process completed with exit code 1.
|
checks / test (3.12, lowest-direct, ubuntu-latest)
Failed to restore: Cache service responded with 400
|
checks / test (3.13, lowest-direct, ubuntu-latest)
Failed to restore: Cache service responded with 400
|
checks / test (3.11, lowest-direct, ubuntu-latest)
Failed to restore: Cache service responded with 400
|
checks / test (3.10, highest, ubuntu-latest)
Failed to restore: Cache service responded with 400
|
checks / test (3.11, highest, ubuntu-latest)
Failed to restore: Cache service responded with 400
|
checks / test (3.12, highest, ubuntu-latest)
Failed to restore: Cache service responded with 400
|
checks / test (3.10, lowest-direct, ubuntu-latest)
Failed to restore: Cache service responded with 400
|
checks / test (3.13, highest, ubuntu-latest)
Failed to restore: Cache service responded with 400
|
checks / test (3.10, highest, windows-latest)
Failed to restore: Cache service responded with 400
|
checks / test (3.10, lowest-direct, windows-latest)
Failed to restore: Cache service responded with 400
|
checks / test (3.11, lowest-direct, windows-latest)
Failed to restore: Cache service responded with 400
|
checks / test (3.12, lowest-direct, windows-latest)
Failed to restore: Cache service responded with 400
|
checks / test (3.11, highest, windows-latest)
Failed to restore: Cache service responded with 400
|
checks / test (3.12, highest, windows-latest)
Failed to restore: Cache service responded with 400
|
checks / test (3.13, highest, windows-latest)
Failed to restore: Cache service responded with 400
|
checks / test (3.13, lowest-direct, windows-latest)
Failed to restore: Cache service responded with 400
|
checks / test (3.10, highest, 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.10, lowest-direct, 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, lowest-direct, 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, lowest-direct, 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, highest, 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, highest, 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, highest, 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, lowest-direct, 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
|