Andreas Enge <[email protected]> writes:
Am Tue, Apr 28, 2026 at 07:23:11AM -0400 schrieb Jason Conroy:
I'd be curious to hear from those who are deeply familiar with
the QA
infrastructure, but I suspect that errors scattered across
thousands of
build logs are an inconvenient signal to consume. If those
errors were
compiled into a dashboard, then sure, but that seems like a
project unto
itself.
For an example, go to
https://qa.guix.gnu.org/branch/python-team
and click on "Failing" or "Blocked" (the latter means that
something has
not been started because an input has failed); and Phong's
example shows
the main culprits the failing of which causes lots of blocked
dependents.
Thanks. At the time of writing that I thought the proposal was to
produce "soft errors" in the logs and somehow inspect those, as
opposed to just letting builds break and tracking the failures.
Jason
