When a test fails in GitHub Actions, you often get thousands of log lines. The main error message is usually something vague, like “Failed to load ApplicationContext.” The real root cause is often buried deeper in the stack trace.
In my case, I was troubleshooting a failure due to a missing property:
defined in application.properties (app) But missing in the test configuration.
The log contained around 15,000 lines, and I wasted a lot of time chasing unrelated exceptions before discovering the real issue.
This extension adds a button to the GitHub Actions UI. It extracts the logs and aims to identify the most relevant “Caused by” line by filtering out common Spring wrapper exceptions such as BeanCreationException and UnsatisfiedDependencyException. It then scores the remaining lines.
It presents:
- the most likely root cause - a short explanation - a suggested fix based on simple pattern matching
I built the first version in about 3 hours, using AI tools to speed up parsing logic and handling edge cases.
It’s still quite basic, but already helpful for common “config/bean” type failures.
I'm interested in whether others have experienced the same issue or found different solutions.