FailTrace tool reproduces failed GitHub Actions runs locally from a run URL
FailTrace is a new command-line tool in early development that takes a failed GitHub Actions run URL and identifies the exact job, step, commit and matrix combination that failed. It matches the failure to the workflow file at that commit, extracts the error from logs, and can set up a Docker-based reproduction of the failing step on a developer's own machine. The tool currently supports three commands—inspect, plan and repro—and works for Linux jobs whose failing step is a run: script.
GoKawiil's interpretation of the reporting above, not reported fact.
By starting from a specific failed run rather than a generic workflow file, FailTrace could reduce the manual guesswork developers face when debugging CI failures, positioning it as a complement to existing tools like act rather than a replacement. Its stated roadmap of adding verdicts such as reproduced, not reproduced, or flaky suggests ambitions to also help teams distinguish genuine bugs from flaky test infrastructure, though this functionality is not yet available.
- FailTrace extracts the exact commit, job, step and matrix combination from a failed GitHub Actions run URL.
- It currently supports Linux jobs with run: script failing steps via Docker-based reproduction.
- Future updates aim to add verdicts like reproduced, not reproduced, or flaky, plus CI-vs-local diffs.
Source: github.com, 2026-11-19
Published there as: “FailTrace – Reproduce a failed GitHub Actions run locally from its URL”
Read the original report → The summary and analysis above are GoKawiil's own, written from reporting by the source above. Facts and quotes belong to the original publisher.