Re: The www/chromium port times out in build on package builders for a long time

On Wed, May 8, 2024 at 3:05 PM Yuri <yuri@freebsd.org> wrote:

> Hi,
>
>
> The chromium package hasn't been available for a while now on 14/amd64.
> The reason is that the build is being killed because it takes too long.
> One solution could be to implement custom timeout value that would be
> possible to set in /usr/local/etc/poudriere.d/{vm_name}-make.conf on a
> per-port basis, like this is done with MAX_FILES.
>
>
> I've suggested this improvement to be made in poudriere:
> https://github.com/freebsd/poudriere/issues/1153
>
>
>
>
> Thanks,
> Yuri
>

To quantify this a bit, all three Chromium-based ports, chromium,
iridium-browser, and ungoogled-chromium timeout in all builds since
24-Dec-2023 for amd64 14.0. The last successful build of the three started
on 17-Dec-2023 and two of the three exceeded 2 days by a few minutes while
chromium completed in 46 hours and 46 minutes.

As it continues to timeout, it is requeued for every subsequent build,
effectively delaying every build cycle which results in larger queue
average sizes for each build taking longer in a slightly positive feedback
loop, though the loop is still relatively stable. This is my main concern
as I don't use any of the three ports. I do see that the average number of
packages that are behind the port seems to be steadily rising, on a system
with only 310 packages installed, from 5-6 to 12-25 and is increasing.

I have not looked at statistics for other builds either by version or
platform.
-- 
Kevin Oberman, Part time kid herder and retired Network Engineer
E-mail: rkoberman@gmail.com
PGP Fingerprint: D03FB98AFA78E3B78C1694B318AB39EF1B055683