Skip to content
Latchkey

Testing workflow (geometric-intelligence/topobench)

The Testing workflow from geometric-intelligence/topobench, explained and optimized by Latchkey.

C

CI health: C - fair

Point runs-on at Latchkey and get run de-duplication, job timeouts, SHA-pinned actions, self-healing for flaky steps, and up to 58% lower cost, applied automatically.

Grade your own workflow free or run it on Latchkey →
Source: geometric-intelligence/topobench.github/workflows/test.ymlLicense MITView source

What it does

This is the Testing workflow from the geometric-intelligence/topobench 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: Testing

on:
  push:
    branches: ["main"]
  pull_request:

permissions:
  contents: read

jobs:
  build:
    runs-on: ubuntu-latest
    strategy:
      matrix:
        python-version: ["3.11"]

    steps:
      - uses: actions/checkout@v4

      # 1. Setup uv
      - name: Install uv
        uses: astral-sh/setup-uv@v5
        with:
          python-version: ${{ matrix.python-version }}
          enable-cache: true
          cache-dependency-glob: "uv.lock"

      # 2. Run your centralized installation script
      - name: Install dependencies (via script)
        run: |
          # This script handles the .venv creation and PyTorch/CUDA logic
          source uv_env_setup.sh

      # 3. Run Tests
      - name: Test with pytest
        run: |
          # We must activate the venv created by your script
          source .venv/bin/activate
          pytest --cov --cov-report=xml:coverage.xml test/

      - name: Upload coverage reports to Codecov
        uses: codecov/codecov-action@v4.0.1
        with:
          token: ${{ secrets.CODECOV_TOKEN }}
          file: coverage.xml
          fail_ci_if_error: false

The same workflow, on Latchkey

Removes redundant runs and caps runaway jobs. Added and changed lines are highlighted.

name: Testing
 
on:
  push:
    branches: ["main"]
  pull_request:
 
permissions:
  contents: read
 
concurrency:
  group: ${{ github.workflow }}-${{ github.ref }}
  cancel-in-progress: true
 
jobs:
  build:
    timeout-minutes: 30
    runs-on: latchkey-small
    strategy:
      matrix:
        python-version: ["3.11"]
 
    steps:
      - uses: actions/checkout@v4
 
      # 1. Setup uv
      - name: Install uv
        uses: astral-sh/setup-uv@v5
        with:
          python-version: ${{ matrix.python-version }}
          enable-cache: true
          cache-dependency-glob: "uv.lock"
 
      # 2. Run your centralized installation script
      - name: Install dependencies (via script)
        run: |
          # This script handles the .venv creation and PyTorch/CUDA logic
          source uv_env_setup.sh
 
      # 3. Run Tests
      - name: Test with pytest
        run: |
          # We must activate the venv created by your script
          source .venv/bin/activate
          pytest --cov --cov-report=xml:coverage.xml test/
 
      - name: Upload coverage reports to Codecov
        uses: codecov/codecov-action@v4.0.1
        with:
          token: ${{ secrets.CODECOV_TOKEN }}
          file: coverage.xml
          fail_ci_if_error: false
 

What changed

2 third-party actions are referenced by a movable tag. Pin them to the commit SHA (Latchkey resolves and applies this automatically) so a repointed tag cannot change what runs.

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