CI flake: Smoketests (Windows 4/4) #6334

Activity

1. clockwork-labs-bot commented on Oct 19, 2026

   

   clockwork-labs-bot

   on Oct 19, 2026

   ContributorAuthor

   More actions

   Exact-attempt diagnosis

   Inspected run 39285283248, job 118178027148, Smoketests (Windows 4/4), attempt 2. The job API confirms attempt 2; attempt 2 -> 3 in the ticket describes the detector transition, not a different linked attempt. Context: PR #6116, head 6ada356f5e377c995859b68ffaa6a9220d8fe4c1; checkout merge 581ac70d2a32e7e1f02c644eb1b9b4c91edf97f2 in the component jobs. Diagnosis is limited to this linked job/attempt.

   The job failed in Install psql, before artifact downloads or the Windows smoketest partition ran:

   • Command: choco install psql -y --no-progress.
   • The failed V2 feed lookup was for psql, version 18.6.5: 503 (Service Unavailable). Chocolatey then reported Unable to find package 'psql' and installed no packages. The explicit Get-Command psql verification failed: The term 'psql' is not recognized as a name of a cmdlet, function, script file, or executable program.
   • The step ended with Process completed with exit code 1.

   Root cause visible in this attempt: the external Chocolatey community package feed (community.chocolatey.org/api/v2/) returned HTTP 503, preventing installation of the runner's PostgreSQL client dependency. This is a dependency-setup/infrastructure flake, not a smoketest assertion or compile failure. The detector's cargo-timings-smoketests- excerpt comes from the later timing upload step, which succeeded and did not cause the failure. Bounded install retries or provisioning psql in the runner image would avoid making each test shard depend on a live package-feed request.

   Suggested updated title: CI flake: Windows smoketests Chocolatey psql install fails with HTTP 503

   Duplicate analysis

   Searched open and closed issues using broad psql, chocolatey, and chocolatey 503 terms; inspected the matching Test flakes tickets and closed-repeat discussion.

   • Top duplicate candidate: CI flake: Windows failed to install psql #5741, the open tracker for Windows Chocolatey psql installation/feed failures.
   • Open repeats CI flake: Smoketests (Windows 2/4) #6292, CI flake: Smoketests (Windows 1/4) #5945 and CI flake: Smoketests (Windows 2/4) #5915 explicitly document the same HTTP 503 -> missing psql setup mechanism. CI flake: Smoketests (Windows) - psql not found #5386 is an older missing-psql tracker with less precise cause evidence.
   • Closed repeat CI flake: Smoketests (Windows 4/4) #5754 was subsequently closed in favor of CI flake: Windows failed to install psql #5741; report CI flake: Windows failed to install psql #5741 rather than that intermediate repeat.
   • Same-run reports CI flake: Smoketests (Windows 2/4) #6331, CI flake: Smoketests (Windows 1/4) #6332, CI flake: Smoketests (Windows 3/4) #6333 are sibling occurrences of this setup outage, not separate canonical trackers.
   • This is not the Linux apt/dpkg lock mechanism in CI flake: Could not get lock /var/lib/dpkg/lock-frontend #5273 or the Windows runner-loss/no-log mechanism in CI flake - Windows self-hosted runner loses communication with GitHub #5799: this job has explicit Chocolatey HTTP 503 logs.

   Leaving open: #5741 is not an authorized automatic duplicate-closure target.
2. bfops

   closed this as a duplicateof CI flake: Windows failed to install psql #5741 on Oct 20, 2026