package-test workflow (GoogleChrome/lighthouse)

The package-test workflow from GoogleChrome/lighthouse, explained and optimized by Latchkey.

What it does

This is the package-test workflow from the GoogleChrome/lighthouse repository, a real project running GitHub Actions. It is shown here with attribution under its Apache-2.0 license.

Below, Latchkey shows a faster, safer version produced by its optimization engine.

The workflow

name: package-test

on:
  push:
    branches: [main]
  pull_request: # run on all PRs, not just PRs to a particular branch

env:
  PUPPETEER_SKIP_DOWNLOAD: 1

jobs:
  package-test:
    runs-on: ubuntu-latest
    name: Package Test
    env:
      FORCE_COLOR: true

    steps:
    - name: git clone
      uses: actions/checkout@v4

    - name: Use Node.js 22.19
      uses: actions/setup-node@v4
      with:
        node-version: '22.19'

    - run: yarn install --frozen-lockfile --network-timeout 1000000
    - run: yarn build-report

    - run: bash $GITHUB_WORKSPACE/core/scripts/release/package-test.sh

    # Fail if any changes were written to source files.
    - run: git diff --exit-code

The same workflow, on Latchkey

Estimated ~20% faster on cache hits, plus fewer wasted runs and a safer supply chain. Added and changed lines are highlighted.

name: package-test
 
on:
  push:
    branches: [main]
  pull_request: # run on all PRs, not just PRs to a particular branch
 
env:
  PUPPETEER_SKIP_DOWNLOAD: 1
 
concurrency:
  group: ${{ github.workflow }}-${{ github.ref }}
  cancel-in-progress: true
 
jobs:
  package-test:
    timeout-minutes: 30
    runs-on: latchkey-small
    name: Package Test
    env:
      FORCE_COLOR: true
 
    steps:
    - name: git clone
      uses: actions/checkout@v4
 
    - name: Use Node.js 22.19
      uses: actions/setup-node@v4
      with:
        cache: 'npm'
        node-version: '22.19'
 
    - run: yarn install --frozen-lockfile --network-timeout 1000000
    - run: yarn build-report
 
    - run: bash $GITHUB_WORKSPACE/core/scripts/release/package-test.sh
 
    # Fail if any changes were written to source files.
    - run: git diff --exit-code
 

What changed

• Run on Latchkey managed runners with one line (runs-on), which apply the fixes below automatically and self-heal transient failures. This example uses latchkey-small; pick the runner size that fits the job.
• Cancel superseded runs when a branch or PR gets a newer push.
• Cache dependency installs on the setup step so they are served from cache.
• Add a job timeout so a hung step cannot burn hours of runner time.

What Latchkey heals here

This workflow has steps that commonly fail on transient issues (network, registries, flaky browsers). On Latchkey managed runners they are detected, retried, and self-healed instead of failing your build:

• Dependency installs

This workflow runs 1 job per trigger. On Latchkey the same minutes cost up to 58% less than GitHub-hosted, with zero queue time.

Actions used in this workflow