Cron Calendar
Explain cron expressions and preview the next run times in any timezone.
OpenTurn a CI artifact into a short failure summary you can paste into a pull request.
SARIF, JUnit XML, Lighthouse JSON, or raw logs.
Findings cluster into actionable lists.
Paste a concise failure summary into pull requests.
Pair with Secrets Redactor when logs may contain tokens.
The build is red, the JUnit report is 3,000 lines of XML, and the reviewer just wants to know which tests broke. Downloading the artifact and grepping it works, but it is slow every time. CI Failure Studio detects what you pasted and pulls out the failures.
The input type is detected automatically. XML is read as JUnit, and every testcase is listed with its suite, class, time and failure or error message. JSON with a runs array or a SARIF schema becomes a findings list with rule ID, level, message, file and line. Lighthouse JSON yields category scores out of 100 and the audits scoring below 0.9. Anything else is treated as a plain log: lines mentioning error, failed, exception or fatal are collected, numbers are normalised so repeats group together, and the 20 most frequent patterns are listed. The full result appears as JSON, and Copy Markdown produces a summary for a PR comment, capped at 30 entries for SARIF and JUnit.
For long unstructured logs, the log template clustering tool adds threshold control and anomaly detection that the simple log mode here lacks. Scrub the output before posting it publicly, since CI logs often echo environment variables; the local log redactor handles the common token formats. If the workflow file itself needs fixing, try the workflow builder for GitHub Actions.
Parsing uses the browser's DOMParser and JSON.parse, entirely in the page, so internal test names and file paths are not shared with an outside service.
Keyboard shortcut
Answers for this tool. For site-wide help, open the FAQ hub.
Text starting with < is parsed as JUnit XML. JSON with a SARIF $schema or a runs array is treated as SARIF, and JSON with both categories and audits as a Lighthouse report. Everything else falls back to log mode.
Yes, when they are saved as JUnit XML, which both can produce (pytest with --junitxml, Jest with the jest-junit reporter). Their plain console output works too, but only through the simpler log mode.
The Markdown summary lists failed tests only, up to 30. Passing tests and any failures beyond the first 30 are still in the JSON report.