Unit tests + static analysis workflow (whyhow-ai/knowledge-graph-studio)

The Unit tests + static analysis workflow from whyhow-ai/knowledge-graph-studio, explained and optimized by Latchkey.

What it does

This is the Unit tests + static analysis workflow from the whyhow-ai/knowledge-graph-studio 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

name: Unit tests + static analysis

on:
  pull_request:
  push:
    branches: [main]

jobs:
  build:
    runs-on: ${{ matrix.os }}
    strategy:
      matrix:
        os: [ubuntu-latest]
        python-version: ["3.10"]

    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 Python dependencies
        run: |
          python -m pip install --upgrade pip
          pip install 'fastapi==0.110.3'
          pip install -e .[dev]

      - name: Lint with flake8
        run: |
          flake8 src tests

      - name: Check style with black
        run: |
          black --check src tests

      - name: Run security check
        run: |
          bandit -qr -c pyproject.toml src

      - name: Run import check
        run: |
          isort --check src tests

      - name: Run mypy
        run: |
          mypy src

      - name: Run unit tests with pytest
        run: |
          pytest --color=yes tests/unit

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: Unit tests + static analysis
 
on:
  pull_request:
  push:
    branches: [main]
 
concurrency:
  group: ${{ github.workflow }}-${{ github.ref }}
  cancel-in-progress: true
 
jobs:
  build:
    timeout-minutes: 30
    runs-on: ${{ matrix.os }}
    strategy:
      matrix:
        os: [ubuntu-latest]
        python-version: ["3.10"]
 
    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 Python dependencies
        run: |
          python -m pip install --upgrade pip
          pip install 'fastapi==0.110.3'
          pip install -e .[dev]
 
      - name: Lint with flake8
        run: |
          flake8 src tests
 
      - name: Check style with black
        run: |
          black --check src tests
 
      - name: Run security check
        run: |
          bandit -qr -c pyproject.toml src
 
      - name: Run import check
        run: |
          isort --check src tests
 
      - name: Run mypy
        run: |
          mypy src
 
      - name: Run unit tests with pytest
        run: |
          pytest --color=yes tests/unit
 

What changed

• 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