macos-cp312 workflow (leptonai/leptonai)
The macos-cp312 workflow from leptonai/leptonai, 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 →What it does
This is the macos-cp312 workflow from the leptonai/leptonai repository, a real project running GitHub Actions. It is shown here with attribution under its Apache-2.0 license.
Below, Latchkey shows a faster, safer version produced by its optimization engine.
The workflow
name: macos-cp312
on:
pull_request:
branches: ["**"]
permissions:
contents: read
jobs:
test:
runs-on: macos-latest
steps:
- uses: actions/checkout@v3
- name: Set up Python 3.12
uses: actions/setup-python@v4
with:
python-version: "3.12"
cache: "pip" # caching pip dependencies
- name: Install dependencies
run: |
pip install -U pip setuptools
- name: Test with pytest
env:
PYTORCH_MPS_HIGH_WATERMARK_RATIO: 0.0
run: |
pip install .
echo "leptonai package version:"
lep -v
pip install .[test]
cd ..
pytest -x leptonai
cd -The same workflow, on Latchkey
Removes redundant runs and caps runaway jobs. Added and changed lines are highlighted.
name: macos-cp312 on: pull_request: branches: ["**"] permissions: contents: read concurrency: group: ${{ github.workflow }}-${{ github.ref }} cancel-in-progress: true jobs: test: timeout-minutes: 30 runs-on: macos-latest steps: - uses: actions/checkout@v3 - name: Set up Python 3.12 uses: actions/setup-python@v4 with: python-version: "3.12" cache: "pip" # caching pip dependencies - name: Install dependencies run: | pip install -U pip setuptools - name: Test with pytest env: PYTORCH_MPS_HIGH_WATERMARK_RATIO: 0.0 run: | pip install . echo "leptonai package version:" lep -v pip install .[test] cd .. pytest -x leptonai cd -
What changed
- Cancel superseded runs when a branch or PR gets a newer push.
- 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.