I'm sharing my experience about finding the reason why the build fails. This has been frustrating.
In the past, it has been a challenge to find the reason why the build fails. Not that we don't have the information about the failure, but the challenge is that there's too much information. :) Loading large log files in the GitHub Actions UI usually freezes the browser for some time (10-30 seconds), and it's slow and frustrating to find what caused the build failure. There's an improvement for this now. I improved finding the build failure recently in Pulsar CI. This guide explains how you can view Pulsar CI test failures in a simple and usable way: https://gist.github.com/lhotari/a76feddb9e77f2d316785614cb0a52dd (I'm planning to contribute this to the contributors guide eventually) -Lari
