Skip to content
Latchkey

Test Report workflow (RDFLib/rdflib)

The Test Report workflow from RDFLib/rdflib, explained and optimized by Latchkey.

B

CI health: B - good

Point runs-on at Latchkey and get 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: RDFLib/rdflib.github/workflows/test-report.ymlLicense BSD-3-ClauseView source

What it does

This is the Test Report workflow from the RDFLib/rdflib repository, a real project running GitHub Actions. It is shown here with attribution under its BSD-3-Clause license.

Below, Latchkey shows a faster, safer version produced by its optimization engine.

The workflow

workflow (.yml)
name: "Test Report"
on:
  workflow_run:
    workflows: ["Validate"]
    types:
      - completed
jobs:
  report:
    runs-on: ubuntu-latest
    permissions:
      checks: write
      statuses: write
    steps:
      - uses: dorny/test-reporter@v3
        with:
          artifact: /(.*)-mypy-junit-xml$/
          name: mypy report
          path: "*.xml"
          reporter: java-junit
          fail-on-error: "false"
      - uses: dorny/test-reporter@v3
        with:
          artifact: /(.*)-pytest-junit-xml$/
          name: pytest report
          path: "*.xml"
          reporter: java-junit
          fail-on-error: "false"

The same workflow, on Latchkey

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

name: "Test Report"
on:
  workflow_run:
    workflows: ["Validate"]
    types:
      - completed
jobs:
  report:
    timeout-minutes: 30
    runs-on: latchkey-small
    permissions:
      checks: write
      statuses: write
    steps:
      - uses: dorny/test-reporter@v3
        with:
          artifact: /(.*)-mypy-junit-xml$/
          name: mypy report
          path: "*.xml"
          reporter: java-junit
          fail-on-error: "false"
      - uses: dorny/test-reporter@v3
        with:
          artifact: /(.*)-pytest-junit-xml$/
          name: pytest report
          path: "*.xml"
          reporter: java-junit
          fail-on-error: "false"
 

What changed

1 third-party action is referenced by a movable tag. Pin it 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