Hi,
On 4/29/26 18:04, Jason Conroy wrote:
Hugo Buddelmeijer writes:
E.g. with python-team I failed to add much value the last couple of
weeks because by the time I managed to compile the rust chain, the
branch was rebased, so I never got to the point that I could figure
out which packages failed, let alone fix them. Having a central
server like QA list blocking builds and serve substitutes would solve
both problems.
Re: "list blocking builds", are you envisioning an interface different
from the "Failing" and "Blocked" dashboards that Andreas and Phong
mentioned?
I meant this interface:
https://data.qa.guix.gnu.org/revision/4ad5564e168f702d6d3eb905fe406a5b8f3dc794/blocking-builds
It shows the important packages to fix because they are ranked by number
of dependents that a failed package has.
I have little experience with the "Failing" and "Blocked" dashboards;
that must be this one:
https://qa.guix.gnu.org/branch/python-team/package-changes
That seems pretty useful too, as it shows packages that have changed.
I'll use that too.
But from this discussion I'm learning that relying on these services too
much causes delays for other branches. Maybe I should setup a build
server specifically (or primarily) for the python-team branch. Because
it seems python-team can fill the queue continuously if we want to; and
at least my contributions are limited by lack of build power.
Hugo
