Skip to content
Latchkey

Tests and coverage workflow (danielegrattarola/spektral)

The Tests and coverage workflow from danielegrattarola/spektral, explained and optimized by Latchkey.

F

CI health: F - at risk

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: danielegrattarola/spektral.github/workflows/test.ymlLicense MITView source

What it does

This is the Tests and coverage workflow from the danielegrattarola/spektral 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 and coverage

on: [push, pull_request]

jobs:
  build:

    runs-on: ${{ matrix.os }}
    strategy:
      matrix:
        python-version: ["3.8", "3.9", "3.10", "3.11"]
        os: [ubuntu-latest, macos-latest, windows-latest]

    steps:
    - uses: actions/checkout@v2
    - name: Set up Python ${{ matrix.python-version }}
      uses: actions/setup-python@v2
      with:
        python-version: ${{ matrix.python-version }}
    - name: Setup utilities
      run: |
        python -m pip install --upgrade pip
        python -m pip install pytest coverage codecov
    - name: Install Spektral
      run: |
        python -m pip install .
    - name: Test with pytest and coverage
      run: |
        python -m coverage run --source=. -m pytest
    - name: Upload coverage to Codecov
      uses: codecov/codecov-action@v1

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 and coverage
 
on: [push, pull_request]
 
concurrency:
  group: ${{ github.workflow }}-${{ github.ref }}
  cancel-in-progress: true
 
jobs:
  build:
    timeout-minutes: 30
 
    runs-on: ${{ matrix.os }}
    strategy:
      matrix:
        python-version: ["3.8", "3.9", "3.10", "3.11"]
        os: [ubuntu-latest, macos-latest, windows-latest]
 
    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: Setup utilities
      run: |
        python -m pip install --upgrade pip
        python -m pip install pytest coverage codecov
    - name: Install Spektral
      run: |
        python -m pip install .
    - name: Test with pytest and coverage
      run: |
        python -m coverage run --source=. -m pytest
    - name: Upload coverage to Codecov
      uses: codecov/codecov-action@v1
 

What changed

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:

This workflow runs 1 job (12 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