microsoft/playwright GitHub Actions scorecard

Public GitHub Actions data, last 30 days. Updated .

Data sourced from public GitHub. GitSpider is not affiliated with or endorsed by this repository's owners. Request removal.

4,455 min/mo
recoverable (~50% of CI time) · across 34 patterns · ≈$27/mo
Estimated from wall-clock time · public repos pay $0, $ = private-repo equivalent
See all 34 fixes, each with the exact YAML ↓
32.2%
failure rate, 30d
18m
avg time to recover from a failure
Since : findings 35 → 34 · recoverable ~4,614 → ~4,455 min/mo
35 workflows · 2,500 runs (83.3/day) · 8,910 CI-min (wall-clock) · ≈$53 at private-repo rates (30d)
CI minutes, cost and failure rate are from the latest 500 of 2,500 runs.

Where the minutes go (30d)

MCP~2,871 min · 74 runs
tests 2~2,642 min · 29 runs
tests 1~2,333 min · 63 runs
or track on every push →

Waste detected

Biggest wins first, each with the exact config fix.

Workflow failing almost every run · tests 2

~2642 min/mo · ≈$16/mo

Fails or times out on nearly all recent runs, burning minutes to produce only red, and an always-red workflow usually gets ignored. Fix it, or disable the trigger until it's ready.

Full guide: how to fix this →

Missing dependency cache · tests 2

~793 min/mo · ≈$5/mo

Set `cache: 'gradle'` on your `actions/setup-java` step, or add an `actions/cache@v4` step keyed on your build file.

- uses: actions/setup-java@v4
  with:
    distribution: 'temurin'
    java-version: '21'
    cache: 'gradle'

Full guide: how to fix this →

Missing dependency cache · tests 1

~700 min/mo · ≈$4/mo

Set `cache: 'pnpm'` on your `actions/setup-node` step, or add an `actions/cache@v4` step keyed on your lockfile.

- uses: actions/setup-node@v4
  with:
    node-version: 20
    cache: 'pnpm'

Full guide: how to fix this →

No concurrency control · tests 2

~264 min/mo · ≈$2/mo

Add a `concurrency:` block keyed on branch to cancel superseded runs when devs push twice quickly.

concurrency:
  group: ${{ github.workflow }}-${{ github.ref }}
  cancel-in-progress: true

Full guide: how to fix this →

Missing dependency cache · infra

~110 min/mo · ≈$1/mo

Set `cache: 'pip'` on your `actions/setup-python` step, or add an `actions/cache@v4` step keyed on your requirements/lock file.

- uses: actions/setup-python@v5
  with:
    python-version: '3.12'
    cache: 'pip'

Full guide: how to fix this →

Missing dependency cache · tests BiDi

~86 min/mo · ≈$1/mo

Set `cache: 'npm'` on your `actions/setup-node` step, or add an `actions/cache@v4` step keyed on your lockfile.

- uses: actions/setup-node@v4
  with:
    node-version: 20
    cache: 'npm'

Full guide: how to fix this →

Missing dependency cache · Publish Test Results

~79 min/mo

Set `cache: 'npm'` on your `actions/setup-node` step, or add an `actions/cache@v4` step keyed on your lockfile.

- uses: actions/setup-node@v4
  with:
    node-version: 20
    cache: 'npm'

Full guide: how to fix this →

No concurrency control · infra

~37 min/mo

Add a `concurrency:` block keyed on branch to cancel superseded runs when devs push twice quickly.

concurrency:
  group: ${{ github.workflow }}-${{ github.ref }}
  cancel-in-progress: true

Full guide: how to fix this →

No concurrency control · Publish Test Results

~26 min/mo

Add a `concurrency:` block keyed on branch to cancel superseded runs when devs push twice quickly.

concurrency:
  group: ${{ github.workflow }}
  # no cancel-in-progress on deploys: queued deploys would be dropped

Full guide: how to fix this →

Missing dependency cache · extension

~21 min/mo

Set `cache: 'npm'` on your `actions/setup-node` step, or add an `actions/cache@v4` step keyed on your lockfile.

- uses: actions/setup-node@v4
  with:
    node-version: 20
    cache: 'npm'

Full guide: how to fix this →

Missing dependency cache · Update test results DB

~17 min/mo

Set `cache: 'npm'` on your `actions/setup-node` step, or add an `actions/cache@v4` step keyed on your lockfile.

- uses: actions/setup-node@v4
  with:
    node-version: 20
    cache: 'npm'

Full guide: how to fix this →

Missing dependency cache · Issue triage (Linux)

~2 min/mo

Set `cache: 'npm'` on your `actions/setup-node` step, or add an `actions/cache@v4` step keyed on your lockfile.

- uses: actions/setup-node@v4
  with:
    node-version: 20
    cache: 'npm'

Full guide: how to fix this →

Missing dependency cache · Issue triage (macOS)

~2 min/mo

Set `cache: 'npm'` on your `actions/setup-node` step, or add an `actions/cache@v4` step keyed on your lockfile.

- uses: actions/setup-node@v4
  with:
    node-version: 20
    cache: 'npm'

Full guide: how to fix this →

Also found: 21 more config fixes with negligible recoverable minutes: timeouts, retention, path filters

No job timeout · infra

~0 min/mo

No job sets `timeout-minutes`, so a hung step can run to GitHub's 6-hour default. Add `timeout-minutes` to each job.

jobs:
  build:
    runs-on: ubuntu-latest
    timeout-minutes: 15

Full guide: how to fix this →

No path filters on triggers · infra

~0 min/mo

Runs on every push/PR with no `paths:` filter, so docs-only changes still trigger full CI. Add a `paths:` filter if that's common.

on:
  pull_request:
    paths:
      - 'src/**'
      - 'package.json'

Full guide: how to fix this →

Premium runners (macOS / Windows) · tests 1

~0 min/mo

macOS bills ~10x and Windows ~2x a Linux minute. The cost estimate above assumes Linux, so your real spend is higher. Move any job that doesn't need them to `ubuntu-latest`.

jobs:
  build:
    runs-on: ubuntu-latest  # ~10x cheaper than macos-latest

Full guide: how to fix this →

Premium runners (macOS / Windows) · tests 2

~0 min/mo

macOS bills ~10x and Windows ~2x a Linux minute. The cost estimate above assumes Linux, so your real spend is higher. Move any job that doesn't need them to `ubuntu-latest`.

jobs:
  build:
    runs-on: ubuntu-latest  # ~10x cheaper than macos-latest

Full guide: how to fix this →

Larger hosted runner · tests 2

~0 min/mo

Uses a larger hosted runner, which bills even on public repos (only standard runners are free). Keep big runners for jobs that measurably need the cores.

jobs:
  lint:
    runs-on: ubuntu-latest  # standard runner — free on public repos

Full guide: how to fix this →

No job timeout · Publish Test Results

~0 min/mo

No job sets `timeout-minutes`, so a hung step can run to GitHub's 6-hour default. Add `timeout-minutes` to each job.

jobs:
  build:
    runs-on: ubuntu-latest
    timeout-minutes: 15

Full guide: how to fix this →

No job timeout · tests BiDi

~0 min/mo

No job sets `timeout-minutes`, so a hung step can run to GitHub's 6-hour default. Add `timeout-minutes` to each job.

jobs:
  build:
    runs-on: ubuntu-latest
    timeout-minutes: 15

Full guide: how to fix this →

Scheduled at the top of the hour · tests BiDi

~0 min/mo

The schedule fires at minute :00, GitHub's peak window, where scheduled runs get delayed or skipped. Shift to any other minute for the same cadence with less contention.

on:
  schedule:
    - cron: '50 0 * * *'  # was '0 0 * * *' — any non-:00 minute avoids the herd

Full guide: how to fix this →

System packages reinstalled every run · tests BiDi

~0 min/mo

System packages install from the network on every run with no cache. Cache them (cache-apt-pkgs-action) or check whether the runner image already has the tool.

- uses: awalsh128/cache-apt-pkgs-action@latest
  with:
    packages: <your packages>
    version: 1.0

Full guide: how to fix this →

Tests wrapped in auto-retry · tests BiDi

~0 min/mo

Tests run under an auto-retry wrapper, so each retry re-bills the same minutes and masks the flaky tests it papers over. Track, fix or quarantine the flakes, then drop the wrapper.

Full guide: how to fix this →

No job timeout · MCP

~0 min/mo

No job sets `timeout-minutes`, so a hung step can run to GitHub's 6-hour default. Add `timeout-minutes` to each job.

jobs:
  build:
    runs-on: ubuntu-latest
    timeout-minutes: 15

Full guide: how to fix this →

Premium runners (macOS / Windows) · MCP

~0 min/mo

macOS bills ~10x and Windows ~2x a Linux minute. The cost estimate above assumes Linux, so your real spend is higher. Move any job that doesn't need them to `ubuntu-latest`.

jobs:
  build:
    runs-on: ubuntu-latest  # ~10x cheaper than macos-latest

Full guide: how to fix this →

No job timeout · extension

~0 min/mo

No job sets `timeout-minutes`, so a hung step can run to GitHub's 6-hour default. Add `timeout-minutes` to each job.

jobs:
  build:
    runs-on: ubuntu-latest
    timeout-minutes: 15

Full guide: how to fix this →

Premium runners (macOS / Windows) · extension

~0 min/mo

macOS bills ~10x and Windows ~2x a Linux minute. The cost estimate above assumes Linux, so your real spend is higher. Move any job that doesn't need them to `ubuntu-latest`.

jobs:
  build:
    runs-on: ubuntu-latest  # ~10x cheaper than macos-latest

Full guide: how to fix this →

Scheduled at the top of the hour · Update test results DB

~0 min/mo

The schedule fires at minute :00, GitHub's peak window, where scheduled runs get delayed or skipped. Shift to any other minute for the same cadence with less contention.

on:
  schedule:
    - cron: '6 */3 * * *'  # was '0 */3 * * *' — any non-:00 minute avoids the herd

Full guide: how to fix this →

Artifacts at default retention · Issue triage (Linux)

~0 min/mo

`upload-artifact` has no `retention-days`, so artifacts keep up to 90 days (storage cost). Set e.g. `retention-days: 7`.

- uses: actions/upload-artifact@v4
  with:
    name: build
    path: dist/
    retention-days: 7

Full guide: how to fix this →

Artifacts at default retention · Issue triage (macOS)

~0 min/mo

`upload-artifact` has no `retention-days`, so artifacts keep up to 90 days (storage cost). Set e.g. `retention-days: 7`.

- uses: actions/upload-artifact@v4
  with:
    name: build
    path: dist/
    retention-days: 7

Full guide: how to fix this →

Premium runners (macOS / Windows) · Issue triage (macOS)

~0 min/mo

macOS bills ~10x and Windows ~2x a Linux minute. The cost estimate above assumes Linux, so your real spend is higher. Move any job that doesn't need them to `ubuntu-latest`.

jobs:
  build:
    runs-on: ubuntu-latest  # ~10x cheaper than macos-latest

Full guide: how to fix this →

Missing dependency cache · Issue triage (Windows)

~0 min/mo

Set `cache: 'npm'` on your `actions/setup-node` step, or add an `actions/cache@v4` step keyed on your lockfile.

- uses: actions/setup-node@v4
  with:
    node-version: 20
    cache: 'npm'

Full guide: how to fix this →

Artifacts at default retention · Issue triage (Windows)

~0 min/mo

`upload-artifact` has no `retention-days`, so artifacts keep up to 90 days (storage cost). Set e.g. `retention-days: 7`.

- uses: actions/upload-artifact@v4
  with:
    name: build
    path: dist/
    retention-days: 7

Full guide: how to fix this →

Premium runners (macOS / Windows) · Issue triage (Windows)

~0 min/mo

macOS bills ~10x and Windows ~2x a Linux minute. The cost estimate above assumes Linux, so your real spend is higher. Move any job that doesn't need them to `ubuntu-latest`.

jobs:
  build:
    runs-on: ubuntu-latest  # ~10x cheaper than macos-latest

Full guide: how to fix this →

Copy every fix as one block (14 snippets, annotated per workflow)
# Missing dependency cache (gradle) (applies to: tests 2)
- uses: actions/setup-java@v4
  with:
    distribution: 'temurin'
    java-version: '21'
    cache: 'gradle'

# Missing dependency cache (pnpm) (applies to: tests 1)
- uses: actions/setup-node@v4
  with:
    node-version: 20
    cache: 'pnpm'

# No concurrency control (applies to: tests 2, infra)
concurrency:
  group: ${{ github.workflow }}-${{ github.ref }}
  cancel-in-progress: true

# Missing dependency cache (pip) (applies to: infra)
- uses: actions/setup-python@v5
  with:
    python-version: '3.12'
    cache: 'pip'

# Missing dependency cache (npm) (applies to: tests BiDi, Publish Test Results, extension, Update test results DB, Issue triage (Linux), Issue triage (macOS), Issue triage (Windows))
- uses: actions/setup-node@v4
  with:
    node-version: 20
    cache: 'npm'

# No concurrency control (applies to: Publish Test Results)
concurrency:
  group: ${{ github.workflow }}
  # no cancel-in-progress on deploys: queued deploys would be dropped

# No job timeout (applies to: infra, Publish Test Results, tests BiDi, MCP, extension)
jobs:
  build:
    runs-on: ubuntu-latest
    timeout-minutes: 15

# No path filters on triggers (applies to: infra)
on:
  pull_request:
    paths:
      - 'src/**'
      - 'package.json'

# Premium runners (macOS / Windows) (applies to: tests 1, tests 2, MCP, extension, Issue triage (macOS), Issue triage (Windows))
jobs:
  build:
    runs-on: ubuntu-latest  # ~10x cheaper than macos-latest

# Larger hosted runner (applies to: tests 2)
jobs:
  lint:
    runs-on: ubuntu-latest  # standard runner — free on public repos

# Scheduled at the top of the hour (applies to: tests BiDi)
on:
  schedule:
    - cron: '50 0 * * *'  # was '0 0 * * *' — any non-:00 minute avoids the herd

# System packages reinstalled every run (applies to: tests BiDi)
- uses: awalsh128/cache-apt-pkgs-action@latest
  with:
    packages: <your packages>
    version: 1.0

# Scheduled at the top of the hour (applies to: Update test results DB)
on:
  schedule:
    - cron: '6 */3 * * *'  # was '0 */3 * * *' — any non-:00 minute avoids the herd

# Artifacts at default retention (applies to: Issue triage (Linux), Issue triage (macOS), Issue triage (Windows))
- uses: actions/upload-artifact@v4
  with:
    name: build
    path: dist/
    retention-days: 7

Each snippet is representative. Merge into the named workflow files rather than pasting wholesale.

Add the badge to your README

Live CI-health badge → GitSpider badge

[![GitSpider](https://gitspider.com/badge/microsoft/playwright.svg)](https://gitspider.com/scan/microsoft/playwright)

Want this on every push?

This scorecard is a one-time snapshot. Install the free GitHub App to track this repo continuously: new regressions caught as they land, trends over time, on your public and private repos. Team adds the offending commit on the PR + Slack alerts.

Install & monitor this repo →

💬 On Team, every PR gets an automatic comment when its CI run fails or runs slow, right where your team already looks. See plans →

Not ready to install? Get this report by email. No spam, unsubscribe anytime.

Share this scorecard: https://gitspider.com/scan/microsoft/playwright