Skip to content

Fix Windows CMake downloads and cache regression timing - #26

Merged
soulteary merged 2 commits into
mainfrom
fix/windows-cmake-download-retries
Nov 9, 2026
Merged

soulteary merged 2 commits into
mainfrom
fix/windows-cmake-download-retries

Conversation

@soulteary

@soulteary soulteary commented Nov 9, 2026 •

Copy link
Copy Markdown
Member

Windows CI had two independent failures:

  • CMake release downloads returned HTTP 504 before configuration. Retry both the archive and checksum downloads up to five times with a five-second interval and 120-second request timeout, retaining mandatory SHA256 verification.
  • The L20Lite configured-speed cache regression hit the default 100ms request deadline on a loaded Windows Release runner while checking an empty cache. Give this cache-semantics test an explicit two-second read budget, preserving all assertions and SDK defaults.

Validation: local Release C++ build passes; configured-speed tests pass (57 assertions across four cases), including the failing regression (14 assertions). All 39 release validation Python tests pass; documentation and helper checks pass (one platform-specific transport test skipped). PR workflows validate Windows and the full platform matrix.

@soulteary soulteary changed the title Retry transient Windows CMake download failures Fix Windows CMake downloads and cache regression timing Nov 9, 2026
@soulteary
soulteary merged commit 2a3d964 into main Nov 9, 2026
23 checks passed
@soulteary
soulteary deleted the fix/windows-cmake-download-retries branch November 9, 2026 13:04
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant