Skip site navigation (1)Skip section navigation (2)
Date:      Thu, 9 May 2024 09:52:36 -0700
From:      Kevin Oberman <rkoberman@gmail.com>
To:        Yuri <yuri@freebsd.org>
Cc:        "ports@freebsd.org" <ports@freebsd.org>
Subject:   Re: The www/chromium port times out in build on package builders for a long time
Message-ID:  <CAN6yY1vAp9ZGOU2Rfb8KSAcnUOX5q73KLnmkVcH1Z2fd1LJD5Q@mail.gmail.com>
In-Reply-To: <1c4b2b99-1bbb-4d7c-ac3a-ac28f3546095@FreeBSD.org>
References:  <1c4b2b99-1bbb-4d7c-ac3a-ac28f3546095@FreeBSD.org>

next in thread | previous in thread | raw e-mail | index | archive | help
--0000000000000480de0618084063
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

On Wed, May 8, 2024 at 3:05=E2=80=AFPM 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.
--=20
Kevin Oberman, Part time kid herder and retired Network Engineer
E-mail: rkoberman@gmail.com
PGP Fingerprint: D03FB98AFA78E3B78C1694B318AB39EF1B055683

--0000000000000480de0618084063
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div dir=3D"ltr"><div class=3D"gmail_default" style=3D"fon=
t-family:tahoma,sans-serif;font-size:small">On Wed, May 8, 2024 at 3:05=E2=
=80=AFPM Yuri &lt;<a href=3D"mailto:yuri@freebsd.org">yuri@freebsd.org</a>&=
gt; wrote:</div></div><div class=3D"gmail_quote"><blockquote class=3D"gmail=
_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204=
,204);padding-left:1ex"><u></u>

 =20

   =20
 =20
  <div>
    <font face=3D"monospace">Hi,</font><br>
    <font face=3D"monospace"><br>
    </font><br>
    <font face=3D"monospace">The chromium package hasn&#39;t been available
      for a while now on 14/amd64.</font><br>
    <font face=3D"monospace">The reason is that the build is being killed
      because it takes too long.</font><br>
    <font face=3D"monospace">One solution could be to implement custom
      timeout value that would be possible to set in <span style=3D"color:r=
gb(0,0,0);background-color:rgb(255,255,255)">/usr/local/etc/poudriere.d/{vm=
_name}-make.conf</span>
      on a per-port basis, like this is done with MAX_FILES.</font><br>
    <font face=3D"monospace"><br>
    </font><br>
    <font face=3D"monospace">I&#39;ve suggested this improvement to be made=
 in
      poudriere: <a href=3D"https://github.com/freebsd/poudriere/issues/115=
3" target=3D"_blank">https://github.com/freebsd/poudriere/issues/1153</a></=
font><br>
    <p><br>
    </p>
    <font face=3D"monospace"><br>
    </font><br>
    <font face=3D"monospace">Thanks,</font><br>
    <font face=3D"monospace">Yuri</font>
    </div></blockquote><div><br></div><div style=3D"font-family:tahoma,sans=
-serif;font-size:small" class=3D"gmail_default">To quantify this a bit, all=
 three Chromium-based ports, chromium, iridium-browser, and ungoogled-chrom=
ium timeout in all builds since 24-Dec-2023 for amd64 14.0. The last succes=
sful build of the three started on 17-Dec-2023 and two of the three exceede=
d 2 days by a few minutes while chromium completed in 46 hours and 46 minut=
es.</div><div style=3D"font-family:tahoma,sans-serif;font-size:small" class=
=3D"gmail_default"><br></div><div style=3D"font-family:tahoma,sans-serif;fo=
nt-size:small" class=3D"gmail_default">As it continues to timeout, it is re=
queued for every subsequent build, effectively delaying every build cycle w=
hich results in larger queue average sizes for each build taking longer in =
a slightly positive feedback loop, though the loop is still relatively stab=
le. This is my main concern as I don&#39;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. <br></div><div style=3D"font-family:tahoma,sans=
-serif;font-size:small" class=3D"gmail_default"><br></div><div style=3D"fon=
t-family:tahoma,sans-serif;font-size:small" class=3D"gmail_default">I have =
not looked at statistics for other builds either by version or platform.<br=
></div></div><span class=3D"gmail_signature_prefix">-- </span><br><div dir=
=3D"ltr" class=3D"gmail_signature"><div dir=3D"ltr"><div><div dir=3D"ltr"><=
div><div dir=3D"ltr"><div><div dir=3D"ltr">Kevin Oberman, Part time kid her=
der and retired Network Engineer<br>E-mail: <a href=3D"mailto:rkoberman@gma=
il.com" target=3D"_blank">rkoberman@gmail.com</a><br></div><div>PGP Fingerp=
rint: D03FB98AFA78E3B78C1694B318AB39EF1B055683</div></div></div></div></div=
></div></div></div></div>

--0000000000000480de0618084063--



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAN6yY1vAp9ZGOU2Rfb8KSAcnUOX5q73KLnmkVcH1Z2fd1LJD5Q>