Re: Indication of build failure from substitute servers?

[pelzflorian (Florian Pelz)]

Marek Paśnikowski <marek@marekpasnikowski.pl> writes:
> The proof of availability is in workflow itself. The project committers
> NEVER commit anything to the master branch. Only the CI system
> does. Instead, the committers push to a "pre-main" branch, and the CI
> system picks the commits up one by one and attempts to build them as
> usual. IMPORTANT POINT: *if* the commit builds correctly, it gets pushed
> by CI to master branch, and the substitute is already available. *If*
> the commit does not build, it gets rejected, and it never goes to
> master.

In theory we have QA badges on patches at the top of
e.g. <https://issues.guix.gnu.org/72101>.  Committers could wait for it
and for its substitutes.

In practice, QA is too slow or does not prioritize enough yet. [1]

Regards,
Florian

[1]
https://lists.gnu.org/archive/html/bug-guix/2024-05/msg00116.html
https://yhetil.org/guix-bugs/87le4czh0z.fsf@gmail.com/