Skip to content
Latchkey

Update angr workflow (decompiler-explorer/decompiler-explorer)

The Update angr workflow from decompiler-explorer/decompiler-explorer, explained and optimized by Latchkey.

A

CI health: A - excellent

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

Grade your own workflow free or run it on Latchkey →
Source: decompiler-explorer/decompiler-explorer.github/workflows/update-angr.ymlLicense MITView source

What it does

This is the Update angr workflow from the decompiler-explorer/decompiler-explorer 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: Update angr

on:
  schedule:
    - cron: '0 19 * * 2' # angr releases at 0 17 * * 2
  workflow_dispatch:

jobs:
  update:
    name: Create angr update PR
    runs-on: ubuntu-22.04
    steps:
      - name: Checkout repo
        uses: actions/checkout@v3
      - name: Install script dependencies
        run: pip install --user feedparser
      - name: Get latest angr version
        run: ./.github/workflows/update-angr.sh
        env:
          GH_TOKEN: ${{ github.token }}

The same workflow, on Latchkey

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

name: Update angr
 
on:
  schedule:
    - cron: '0 19 * * 2' # angr releases at 0 17 * * 2
  workflow_dispatch:
 
jobs:
  update:
    timeout-minutes: 30
    name: Create angr update PR
    runs-on: latchkey-small
    steps:
      - name: Checkout repo
        uses: actions/checkout@v3
      - name: Install script dependencies
        run: pip install --user feedparser
      - name: Get latest angr version
        run: ./.github/workflows/update-angr.sh
        env:
          GH_TOKEN: ${{ github.token }}
 

What changed

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 per trigger. On Latchkey the same minutes cost up to 58% less than GitHub-hosted, with zero queue time.

Actions used in this workflow