Test workflow (abseil/abseil-py)
The Test workflow from abseil/abseil-py, explained and optimized by Latchkey.
CI health: C - fair
Point runs-on at Latchkey and get caching, job timeouts, self-healing for flaky steps, and up to 58% lower cost, applied automatically.
What it does
This is the Test workflow from the abseil/abseil-py 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: Test
on: [push, pull_request]
permissions:
contents: read
concurrency:
group: ${{ github.workflow }}-${{ github.event.pull_request.number || github.run_id }}
cancel-in-progress: true
jobs:
test:
if:
github.event_name == 'push' || github.event.pull_request.head.repo.full_name !=
github.repository
runs-on: ${{ matrix.os }}
strategy:
fail-fast: false
matrix:
python-version: ["3.10", "3.11", "3.12", "3.13", "3.14"]
os: [ubuntu-latest, macos-latest, windows-latest]
steps:
- uses: actions/checkout@v4
- name: Set up Python ${{ matrix.python-version }}
uses: actions/setup-python@v5
id: setup_python
with:
python-version: ${{ matrix.python-version }}
allow-prereleases: true
- name: Install virtualenv
run: |
python -m pip install --upgrade pip
python -m pip install --upgrade virtualenv
- name: Run tests
env:
ABSL_EXPECTED_PYTHON_VERSION: ${{ matrix.python-version }}
ABSL_COPY_TESTLOGS_TO: ci-artifacts
shell: bash
run: ci/run_tests.sh
- name: Upload bazel test logs
uses: actions/upload-artifact@v4
with:
name: bazel-testlogs-${{ matrix.os }}-${{ matrix.python-version }}
path: ci-artifacts
checks:
if:
github.event_name == 'push' || github.event.pull_request.head.repo.full_name !=
github.repository
runs-on: ubuntu-latest
strategy:
matrix:
python-version: ["3.12"]
steps:
- uses: actions/checkout@v4
- name: Set up Python ${{ matrix.python-version }}
uses: actions/setup-python@v5
with:
python-version: ${{ matrix.python-version }}
- name: Install dependencies
run: pip install -U mypy
- name: Check types with mypy
run: mypy absl
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: Test on: [push, pull_request] permissions: contents: read concurrency: group: ${{ github.workflow }}-${{ github.event.pull_request.number || github.run_id }} cancel-in-progress: true jobs: test: timeout-minutes: 30 if: github.event_name == 'push' || github.event.pull_request.head.repo.full_name != github.repository runs-on: ${{ matrix.os }} strategy: fail-fast: false matrix: python-version: ["3.10", "3.11", "3.12", "3.13", "3.14"] os: [ubuntu-latest, macos-latest, windows-latest] steps: - uses: actions/checkout@v4 - name: Set up Python ${{ matrix.python-version }} uses: actions/setup-python@v5 id: setup_python with: cache: 'pip' python-version: ${{ matrix.python-version }} allow-prereleases: true - name: Install virtualenv run: | python -m pip install --upgrade pip python -m pip install --upgrade virtualenv - name: Run tests env: ABSL_EXPECTED_PYTHON_VERSION: ${{ matrix.python-version }} ABSL_COPY_TESTLOGS_TO: ci-artifacts shell: bash run: ci/run_tests.sh - name: Upload bazel test logs uses: actions/upload-artifact@v4 with: name: bazel-testlogs-${{ matrix.os }}-${{ matrix.python-version }} path: ci-artifacts checks: timeout-minutes: 30 if: github.event_name == 'push' || github.event.pull_request.head.repo.full_name != github.repository runs-on: latchkey-small strategy: matrix: python-version: ["3.12"] steps: - uses: actions/checkout@v4 - name: Set up Python ${{ matrix.python-version }} uses: actions/setup-python@v5 with: cache: 'pip' python-version: ${{ matrix.python-version }} - name: Install dependencies run: pip install -U mypy - name: Check types with mypy run: mypy absl
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 useslatchkey-small; pick the runner size that fits the job. - 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 2 jobs (16 with the matrix expanded) per trigger. On Latchkey the same minutes cost up to 58% less than GitHub-hosted, with zero queue time.