Skip to content
Latchkey LogoLatchkey home
EnglishPortuguês日本語
Start Free

Latchkey Learn

Flaky tests in CI

Find flaky tests in GitHub Actions, tell a flaky test from a runner failure, retry without hiding real bugs, and fix suites that flake most.

Start here four stops, in order

  1. 01Find flaky tests from run attemptsFlaky tests
  2. 02Flaky Playwright tests in CIFlaky tests
  3. 03Flaky test or the machine?Flaky tests
  4. 04Retry at the right levelFlaky tests

Contents 1 section · 4 entries

Explore other topics
GitHub Actions runners comparedEvery managed runner vendor, priced and benchmarked side by side. GitHub Actions costWhat Actions really costs, and how to cut it. Runner failures Latchkey repairsOut of memory, disk full, rate limits, lost runners: reproduced and fixed. GitHub Actions workflow errorsWorkflow, YAML, permissions and artifact errors, diagnosed and fixed. Docker in CI: Registry, Build & RuntimeRegistry, runtime and build errors on CI runners. Faster GitHub ActionsCaching, parallelism and cold starts, measured.