Integration Tests 🧪 workflow (instadeepai/Mava)

The Integration Tests 🧪 workflow from instadeepai/Mava, explained and optimized by Latchkey.

What it does

This is the Integration Tests 🧪 workflow from the instadeepai/Mava 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: Integration Tests 🧪

on:
  push:
    branches:
      - develop

jobs:
  integration-tests:
    name: "Python ${{ matrix.python-version }} on ubuntu-latest"
    runs-on: ubuntu-latest
    timeout-minutes: 20

    strategy:
      matrix:
        python-version: ["3.12", "3.11"]

    steps:
      - name: Checkout mava
        uses: actions/checkout@v4

      - name: Install uv
        uses: astral-sh/setup-uv@v5
        with:
          version: "0.6.12"
          enable-cache: true
          cache-dependency-glob: "uv.lock"  # invalidate cache when requirements file changes
          python-version: "${{ matrix.python-version }}"

      - uses: actions/setup-python@v5
        with:
            python-version: "${{ matrix.python-version }}"

      - name: Install python dependencies 🔧
        run: uv pip install . --group dev
        env:
          UV_SYSTEM_PYTHON: 1

      - name: Run integration tests 🧪
        run: pytest test/integration_test.py -p no:warnings

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: Integration Tests 🧪
 
on:
  push:
    branches:
      - develop
 
concurrency:
  group: ${{ github.workflow }}-${{ github.ref }}
  cancel-in-progress: true
 
jobs:
  integration-tests:
    name: "Python ${{ matrix.python-version }} on ubuntu-latest"
    runs-on: latchkey-small
    timeout-minutes: 20
 
    strategy:
      matrix:
        python-version: ["3.12", "3.11"]
 
    steps:
      - name: Checkout mava
        uses: actions/checkout@v4
 
      - name: Install uv
        uses: astral-sh/setup-uv@v5
        with:
          version: "0.6.12"
          enable-cache: true
          cache-dependency-glob: "uv.lock"  # invalidate cache when requirements file changes
          python-version: "${{ matrix.python-version }}"
 
      - uses: actions/setup-python@v5
        with:
          cache: 'pip'
            python-version: "${{ matrix.python-version }}"
 
      - name: Install python dependencies 🔧
        run: uv pip install . --group dev
        env:
          UV_SYSTEM_PYTHON: 1
 
      - name: Run integration tests 🧪
        run: pytest test/integration_test.py -p no:warnings
 

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.

1 third-party action is referenced by a movable tag. Pin it to the commit SHA (Latchkey resolves and applies this automatically) so a repointed tag cannot change what runs.

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 (2 with the matrix expanded) per trigger. On Latchkey the same minutes cost up to 58% less than GitHub-hosted, with zero queue time.

Actions used in this workflow