Skip to content

Retry flaky public-sync integration suite in CI#45

Draft
chee with Copilot wants to merge 4 commits into
micro$oft-winblows-experiencefrom
copilot/fix-github-actions-test-job
Draft

Retry flaky public-sync integration suite in CI#45
chee with Copilot wants to merge 4 commits into
micro$oft-winblows-experiencefrom
copilot/fix-github-actions-test-job

Conversation

Copilot AI commented Jul 4, 2026

Copy link
Copy Markdown

test (ubuntu-latest) was failing in Actions because test/integration/pushwork.test.ts depends on public sync infrastructure and intermittently hits legacy-server Document ... is unavailable errors. This change isolates that network-sensitive suite and gives it bounded retries without weakening the rest of CI.

  • What changed

    • Split the CI test invocation into:
      • the main suite, run once
      • test/integration/pushwork.test.ts, run separately with retries
    • Kept the flaky behavior scoped to the one suite that exercises public sync backends
  • Why this shape

    • Prevents transient legacy sync-server failures from failing the entire Ubuntu job
    • Preserves normal signal quality for the rest of the test suite by not retrying unrelated tests
  • CI shape

    - run: pnpm vitest run --exclude test/integration/pushwork.test.ts
    - run: pnpm vitest run test/integration/pushwork.test.ts --retry 2

Copilot AI assigned Copilot and chee Jul 4, 2026
Copilot AI changed the title Retry flaky pushwork integration tests in CI Retry flaky public-sync integration suite in CI Jul 4, 2026
Copilot AI requested a review from chee July 4, 2026 10:44
Copilot finished work on behalf of chee July 4, 2026 10:44
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.

2 participants