AI-Powered Log Detective Now Automates Failed Build Analysis in Packit

Automated Failure Analysis Goes Live

Starting this month, every failed Packit-triggered scratch Koji build on a dist-git pull request will be automatically analyzed by Log Detective. The new integration aims to demystify package build failures, especially for newcomers to Fedora ecosystem maintenance.

“This is a major step in reducing the friction for contributors who hit build errors they don’t understand,” said a Packit developer speaking on condition of anonymity. “Instead of hunting through hundreds of log lines, you get a clear explanation and often a fix suggestion.”

How Log Detective Works in Packit

In Copr, users could already request an analysis by clicking an “Ask AI” button. Now, with Packit, the process is fully automatic: a build failure triggers an analysis request, and the results appear in the Packit dashboard as soon as they are ready.

No additional setup is required. Users do not need to select logs or tune prompts. The service handles everything behind the scenes.

Log Parsing and Analysis Derivation

Starting with version 4.0, Log Detective runs as an agent built on the BeeAI Framework. The agent receives all logs and build artifacts with each analysis request.

Using tools centered on the Drain template mining algorithm, it extracts only the most relevant snippets from the logs. These snippets represent a small fraction of the original log size.

“By focusing on snippets instead of raw logs, we save tokens and cut analysis time,” explained a Log Detective engineer. “This lets us use smaller models while still getting good results.”

Communication Architecture

Packit continues to handle failed Koji builds as before. The difference is that Packit now sends a request to the Log Detective interface server, a lightweight containerized service that manages all communication between the two systems.

Once the analysis is ready, the interface server posts results on the Fedora Messaging bus, where Packit collects them and links them to the triggering pull request.

What the Analysis Delivers

Log Detective provides a clear statement of what went wrong during the build, and optionally suggests a fix. In its current configuration, it uses only the build logs for analysis—not external sources like package maintainer experience.

“The results are presented directly in the Packit dashboard, right next to the PR that failed,” said a Fedora infrastructure team member. “That context is crucial for developers.”

Background

Log Detective was first introduced in Copr, where users manually triggered analysis on failed builds. The tool was well received, prompting the Packit team to integrate it directly into the build failure workflow.

Packit itself has long specialized in bridging upstream projects with downstream distributions like Fedora. The addition of Log Detective extends that integration, turning raw build errors into actionable insights.

What This Means

For experienced package maintainers, Log Detective may offer little new insight. But for newcomers or occasional contributors, it can significantly reduce the learning curve. Instead of deciphering cryptic log entries, they get plain‑language explanations.

“It is not a replacement for experience, but an accelerator,” the Packit developer added. “We hope it makes package maintenance more accessible.”

Future development plans include expanding the tool’s use of sources beyond build logs, potentially covering upstream issue trackers and past build history.

This article was updated at 14:30 UTC with additional context on the communication architecture.