Skip to content

dawn: retry dependency downloads and propagate Git failures - #642

Merged
danoli3 merged 1 commit into
openframeworks:bleedingfrom
danoli3:fix-dawn-dependency-downloads
Oct 15, 2026
Merged

danoli3 merged 1 commit into
openframeworks:bleedingfrom
danoli3:fix-dawn-dependency-downloads

Conversation

@danoli3

@danoli3 danoli3 commented Oct 14, 2026

Copy link
Copy Markdown
Member

Several otherwise successful platform jobs fail while downloading Dawn dependencies: Google-hosted mirrors return HTTP 502/503, and the pinned downloader ignores Git failures. Windows then reaches CMake with an empty SPIRV-Tools directory and reports a missing CMakeLists.txt.

Patch the pinned downloader to retry fetch/clone operations up to three times and propagate exhausted failures. Preserve expected unsuccessful Git probes when recovering partial repositories. Use the original GitHub endpoints for dependencies mirrored from GitHub, retaining their exact DEPS commits. Retry Dawn and depot_tools network fetches too, and increment BUILD_ID to invalidate old outputs.

Validation: patch applies to the pinned upstream script; Python compilation, transient/permanent failure and checkout-error fixtures, Bash syntax, checksum audit and whitespace checks pass. Native platform builds remain pending.

Avoid silently accepting failed dependency fetches and empty checkouts. Retry network Git operations three times, use original GitHub endpoints for Chromium GitHub mirrors, and preserve every pinned DEPS commit.
@danoli3
danoli3 merged commit c5e3d83 into openframeworks:bleeding Oct 15, 2026
22 of 61 checks passed
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