Tests workflow (ZeroIntensity/pointers.py)

The Tests workflow from ZeroIntensity/pointers.py, explained and optimized by Latchkey.

CI health: C - fair

Run this on Latchkey for self-healing, caching, and up to 58% lower cost.

Grade your own workflow free or run it on Latchkey →

Source: ZeroIntensity/pointers.py.github/workflows/tests.ymlLicense MITView source

What it does

This is the Tests workflow from the ZeroIntensity/pointers.py repository, a real project running GitHub Actions. It is shown here with attribution under its MIT license.

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

The workflow

workflow (.yml)

name: Tests


on:
    push:
        branches:
            - master

    pull_request:
        branches:
            - master


concurrency:
    group: test-${{ github.head_ref }}

    cancel-in-progress: true


env:
    PYTHONUNBUFFERED: "1"

    FORCE_COLOR: "1"

    PYTHONIOENCODING: "utf8"


jobs:
    run:
        name: Python ${{ matrix.python-version }} on ${{ startsWith(matrix.os, 'macos-') && 'macOS' || startsWith(matrix.os, 'windows-') && 'Windows' || 'Linux' }}

        runs-on: ${{ matrix.os }}

        strategy:
            fail-fast: false

            matrix:
                os: [ubuntu-latest, windows-latest, macos-latest]

                python-version: ["3.8", "3.9", "3.10", "3.11", "3.12"]


        steps:
            - uses: actions/checkout@v2


            - name: Set up Python ${{ matrix.python-version }}

              uses: actions/setup-python@v2

              with:
                  python-version: ${{ matrix.python-version }}


            - name: Install Ward

              run: pip install --upgrade --pre ward


            - name: Install project

              run: pip install .


            - name: Run tests

              run: ward

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: Tests



on:

    push:

        branches:

            - master

    pull_request:

        branches:

            - master



concurrency:

    group: test-${{ github.head_ref }}

    cancel-in-progress: true



env:

    PYTHONUNBUFFERED: "1"

    FORCE_COLOR: "1"

    PYTHONIOENCODING: "utf8"



jobs:

    run:

        timeout-minutes: 30

        name: Python ${{ matrix.python-version }} on ${{ startsWith(matrix.os, 'macos-') && 'macOS' || startsWith(matrix.os, 'windows-') && 'Windows' || 'Linux' }}

        runs-on: ${{ matrix.os }}

        strategy:

            fail-fast: false

            matrix:

                os: [ubuntu-latest, windows-latest, macos-latest]

                python-version: ["3.8", "3.9", "3.10", "3.11", "3.12"]



        steps:

            - uses: actions/checkout@v2



            - name: Set up Python ${{ matrix.python-version }}

              uses: actions/setup-python@v2

              with:

                  cache: 'pip'

                  python-version: ${{ matrix.python-version }}



            - name: Install Ward

              run: pip install --upgrade --pre ward



            - name: Install project

              run: pip install .



            - name: Run tests

              run: ward

What changed

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 (15 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

actions/checkout actions/setup-python