From nobody Thu May 09 16:52:36 2024 X-Original-To: ports@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4VZykH0W8bz5K4dh for ; Thu, 09 May 2024 16:52:55 +0000 (UTC) (envelope-from kob6558@gmail.com) Received: from mail-yb1-xb29.google.com (mail-yb1-xb29.google.com [IPv6:2607:f8b0:4864:20::b29]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "smtp.gmail.com", Issuer "GTS CA 1D4" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4VZykG5mhvz4Ngd; Thu, 9 May 2024 16:52:54 +0000 (UTC) (envelope-from kob6558@gmail.com) Authentication-Results: mx1.freebsd.org; none Received: by mail-yb1-xb29.google.com with SMTP id 3f1490d57ef6-dcc71031680so1156451276.2; Thu, 09 May 2024 09:52:54 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1715273573; x=1715878373; darn=freebsd.org; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=qYsTQbqG3SMSQNOoGU8Q6I0dzLKM+cyx6hc31Dpymy4=; b=DgCIk8QN/KP4ilXP9dP5gpi/3ZPXZmd8rQCzs5mob+e3XcWsKGAvoAssdSyP4Zu1QA jRimcdP8Zzb/7044R/S7frzZqAH2BsZ5qYNNIfnbgLmNfEzkY+zJBoj8qjM4PxxJ0lSt O+m5n0Jfggj4icerOFU600O121s0IVnmmpL20u3vysFGTDzPkWoCQBOmZSLxp3hT1xu9 rl5bwXihv//W1EMGxsFO4XJ8W0z89eCUPzq8HxktIHRX4ck07fbCCkTV1LP44L/ha+13 YHYavpdudyjQS1rNuWxCsX0bZAymUhxXoGcyyeORhXET5M4c2/F5dJDoYbADpAsg9q9r WRPw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1715273573; x=1715878373; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=qYsTQbqG3SMSQNOoGU8Q6I0dzLKM+cyx6hc31Dpymy4=; b=BMVKdTsyKvufM6WCzB908e4GLJCJFkErfbo+FznwCCOC4opNyHYpF2PFlBF1ZOYbe3 ns4+khEtfipCRDorGkjGaJlfp245AVZQ20Ztu/0/eWQ2PidnumDOidRNUbnYFsaQqrt1 4Hy1wbJaSAap8CaMjGjKrCxi0VEg3n/MxVe/b7sgCODyDRkgEbfixKEdpFTqahZxNKRI pZru8a1RYjLCyPZnbvXx44Af8l3OowlXY3NU75fdxUSjT/QJksXXFrxRqzAWMAkt+oTL lKhy+Q1TXbtVhpivUXPIx3cdmXMCEv3uoJxqUk0V8dFveRyJY6YeRrO9PcV8ZGhX4rIg /kPg== X-Gm-Message-State: AOJu0YwfeccOuRpCU0AJBv9ftnl2tHenQwF3R1R5iSQpSELl0mT35cjW fKKCMp/QP7S+/YJnhsLdzoWudDyWQ1HEF2LO/MudfTJZlgviXe8YlzNbyp0r+K+Z+q3ft7XUL7D iYY4+7MAIsWcq0yDwcU+AOXT5gNvlK5XH X-Google-Smtp-Source: AGHT+IEcCbv/n0EdyQyW1WRVrYKJgzwHNyjbLdkskGcT3luxe51DlWPI4ytcqaDXLaeIuCl70HPeastmqWWB8ORhqGU= X-Received: by 2002:a25:b20b:0:b0:dc6:ff6b:71b2 with SMTP id 3f1490d57ef6-dee4f2f754dmr97943276.4.1715273573101; Thu, 09 May 2024 09:52:53 -0700 (PDT) List-Id: Porting software to FreeBSD List-Archive: https://lists.freebsd.org/archives/freebsd-ports List-Help: List-Post: List-Subscribe: List-Unsubscribe: X-BeenThere: freebsd-ports@freebsd.org Sender: owner-freebsd-ports@FreeBSD.org MIME-Version: 1.0 References: <1c4b2b99-1bbb-4d7c-ac3a-ac28f3546095@FreeBSD.org> In-Reply-To: <1c4b2b99-1bbb-4d7c-ac3a-ac28f3546095@FreeBSD.org> From: Kevin Oberman Date: Thu, 9 May 2024 09:52:36 -0700 Message-ID: Subject: Re: The www/chromium port times out in build on package builders for a long time To: Yuri Cc: "ports@freebsd.org" Content-Type: multipart/alternative; boundary="0000000000000480de0618084063" X-Spamd-Bar: ---- X-Rspamd-Pre-Result: action=no action; module=replies; Message is reply to one we originated X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[]; ASN(0.00)[asn:15169, ipnet:2607:f8b0::/32, country:US] X-Rspamd-Queue-Id: 4VZykG5mhvz4Ngd --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 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
On Wed, May 8, 2024 at 3:05=E2= =80=AFPM Yuri <yuri@freebsd.org&= gt; wrote:
=20 =20 =20
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-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.

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'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.
--
<= div>
Kevin Oberman, Part time kid her= der and retired Network Engineer
E-mail: rkoberman@gmail.com
PGP Fingerp= rint: D03FB98AFA78E3B78C1694B318AB39EF1B055683
--0000000000000480de0618084063--