Test weekly workflow (john-hen/Flake8-pyproject)

The Test weekly workflow from john-hen/Flake8-pyproject, explained and optimized by Latchkey.

What it does

This is the Test weekly workflow from the john-hen/Flake8-pyproject 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

# Regular tests against the current Flake8 main branch.

name: Test weekly


on:
  schedule:
    # Every Saturday at 11:17 UTC.

    - cron: '17 11 * * 6'


jobs:

  flake8_main:

    runs-on: ubuntu-latest


    steps:
      - name: Check out code.

        uses: actions/checkout@v7


      - name: Set up latest stable Python.

        uses: actions/setup-python@v6

        with:
            python-version: '3.x'


      - name: Install current Flake8 main branch.

        run:  pip install git+https://github.com/PyCQA/flake8.git


      - name: Install project.

        run:  pip install .[dev]


      - name: Run tests.

        run:  pytest

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.

# Regular tests against the current Flake8 main branch.

name: Test weekly



on:

  schedule:

    # Every Saturday at 11:17 UTC.

    - cron: '17 11 * * 6'



jobs:



  flake8_main:



    runs-on: latchkey-small



    steps:

      - name: Check out code.

        uses: actions/checkout@v7



      - name: Set up latest stable Python.

        uses: actions/setup-python@v6

        with:

          cache: 'pip'

            python-version: '3.x'



      - name: Install current Flake8 main branch.

        run:  pip install git+https://github.com/PyCQA/flake8.git



      - name: Install project.

        run:  pip install .[dev]



      - name: Run tests.

        run:  pytest

 

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.
• Cache dependency installs on the setup step so they are served from cache.

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