You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Windows clock diagnostic fails with HTTP 404 on HEAD /rate_limit #2961
Workflow: Inspect Windows runner clock offsets (.github/workflows/ci.yml)
Jobs: windows-4 and windows-16
Platform: Namespace Windows Server 2022 x86-64, runner profiles namespace-profile-windows-2022-x86-64-4 and namespace-profile-windows-2022-x86-64-16x32
Attempt: 1; manually dispatched on zb/native-cache-clock-diagnostic-20261024
Both jobs fail in Compare runner and server clocks on their first request:
Invoke-WebRequest : The remote server returned an error: (404) Not Found.
Process completed with exit code 1.
At commit 4409be9, both scripts use Invoke-WebRequest -Method Head against https://api.github.com/rate_limit with a randomized clock_probe query parameter. Read-only probes independently reproduced HTTP 404 for HEAD and HTTP 200 for GET.
Use a supported request method, such as GET, and read the response Date header. The current request prevents either job from collecting clock measurements. These are two occurrences of the same workflow defect, not evidence of runner clock skew or a transient outage.
The diagnostic is absent from main and has no associated pull request. No matching issue or pull request was found.
Activity