triage-ci-flake

Reproducing flaky CI test failures locally requires running the specific failing test in both development and production build environments to isolate whether timing, bundling, or environment differences cause the issue.

Vitest or Playwright tests may fail in CI due to timing issues, bundling discrepancies, or environment differences between local machines and CI pipelines, requiring systematic local reproduction to resolve.

Reproducing a CI test failure locally involves a mandatory workflow of executing the failing test against development code first, followed by a bundled production build, to identify the exact failure environment.

Yes, the triage workflow applies to flaky test failures across testing frameworks like Vitest and Playwright, systematically addressing environment differences and timing issues found in CI pipelines.

Debugging dev builds checks for basic logic or timing failures, while debugging production builds identifies issues introduced during bundling, helping isolate whether the CI flake stems from code or the build process.