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
[Chore] Harden E2E workflow against VS Code binary download failures (Zoo-Code-Org#1045)
* ci: harden E2E workflow against VS Code binary download failures
Add restore-keys fallback to the VS Code test binary cache, probe the VS
Code update API before running tests, fall back to a stale cached binary
(via VSCODE_VERSION) when the CDN is unreachable, and retry the mocked
E2E step so transient network blips don't fail the merge queue. Skip
writing the pass marker when the stale-binary fallback was used.
ClosesZoo-Code-Org#1044
* ci: scope E2E retries to binary download, probe CDN endpoint, prune stale binaries
Address review feedback on Zoo-Code-Org#1045:
- Retry only the VS Code binary download (its own step), so genuine
test failures fail fast instead of re-running the whole suite.
- Probe the archive CDN endpoint (via the 302-redirect HEAD) in
addition to the update API, so the stale-binary fallback also
engages when only the CDN host is down.
- Restore/save the binary cache with restore+save actions and prune
older vscode-linux-x64-* dirs so each saved entry keeps one binary
instead of growing with every version bump; skip the save when the
stale fallback was used.
- Emit a ::warning:: when endpoints are unreachable with no cached
binary, and echo why the pass marker is skipped on fallback runs.
---------
Co-authored-by: Roomote <roomote@roomote.dev>
Co-authored-by: edelauna <54631123+edelauna@users.noreply.github.com>
0 commit comments