From nobody Tue May 23 10:40:19 2023 X-Original-To: freebsd-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 4QQW750MYhz4CK6c; Tue, 23 May 2023 10:40:33 +0000 (UTC) (envelope-from eduardo@freebsd.org) Received: from smtp.freebsd.org (smtp.freebsd.org [96.47.72.83]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "smtp.freebsd.org", Issuer "R3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4QQW745tr4z3KhK; Tue, 23 May 2023 10:40:32 +0000 (UTC) (envelope-from eduardo@freebsd.org) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=freebsd.org; s=dkim; t=1684838432; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: in-reply-to:in-reply-to:references:references; bh=UMusUeoZwWiKjNejRA6TYxnoNXzV8XRv3dydViwL/uc=; b=R1Kol7JKuBpaW3i0Ypg9mYsfZnm6MsPdM77h8pgJ4vJliNYpcPU9B8M2ts4rk4cAO5xD2p wpuC1aETa6ugSSZ7eWVzOoroCVJdIi++AOc4H3Kw5/xKJliybbLyymYWZVRcBw8nBPeMn1 ghaBIHRvctxxe+iu36nVWqK5ABxuEN6NehDrZ6k6Kz/F336+ESAoTy8cjhF0kZjNFhu17N spGCvL6NWMVjOrs5sz7pD4e83BjCHkikW9+irX9MK9ZtlIkMihqOsyGCM1HXjCPLL+TMTJ +KfKp4xm7SLFuuQdQryH/qqdGzjcWK6+WWBJCuajm5gBG7NPCuN5hASjaPHX5Q== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=freebsd.org; s=dkim; t=1684838432; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: in-reply-to:in-reply-to:references:references; bh=UMusUeoZwWiKjNejRA6TYxnoNXzV8XRv3dydViwL/uc=; b=XR+YyRd/vrU4D47s/XQac9QGuHYI0tAAs73H4BmalHZTHP3+d8t8BvrGOQnxYkruvw9TmP QicJ9YHONlKxJhNbGKqlV2Llyx+wzISmFp92CQfPjt2eDvg2l8N2C3WtUVHXe3MAswv29v L4HauFQv1itx4pG1cy+kvmjnmlaHrmnrpgbHWk3WxglteHaN0Ab5UcAhDGut13I4hUX0gs d1a4YR9gs23Vgu8Wta1BZXz2KQWdhePWxWyIo5Ags0FxK6W8u4dhJCgp/Fnz6mVgfeLaF2 ivdppJwypZNiZDNQU0B6xnjBcNIe8fvZ/P8gbnkrmLl3Odgza8vTfcQWXkR9xA== ARC-Authentication-Results: i=1; mx1.freebsd.org; none ARC-Seal: i=1; s=dkim; d=freebsd.org; t=1684838432; a=rsa-sha256; cv=none; b=mTfCM3cZ768xmfin9vwYnyJ1yiwh2uMBRZPSaK1xl3dNdSQTOTPWyMG01rYI5Z45pzWkxv yy1ImoAA2Ppu60A0OWyxaKxVO7lwiY+8SqPnCxIlagJT9R/FJUuBO/x6UsK+xGCyTuOXWa fbZbOXC/uXcwd4CH8aielbXGx+5ic7TP4pHfpMWfW+H7RWumkMLfw2J6p2BjMuoPnyeN5m 6qZFN88AKyWOIN2/y+qJoGcjMRRfQvIsV+xani6k3WJyNQvyfqwTHGp5vFCZmBtFZUVBzo e7JXIaHkb0e4Jm4uHm1c1umEkV5NibHeJ0fqte9FjyqFVVtPpbaMUkXkrsMT+A== Received: from mail-pl1-f173.google.com (mail-pl1-f173.google.com [209.85.214.173]) (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)) (Authenticated sender: eduardo) by smtp.freebsd.org (Postfix) with ESMTPSA id 4QQW744wmxzV8M; Tue, 23 May 2023 10:40:32 +0000 (UTC) (envelope-from eduardo@freebsd.org) Received: by mail-pl1-f173.google.com with SMTP id d9443c01a7336-1ae79528d4dso48013365ad.2; Tue, 23 May 2023 03:40:32 -0700 (PDT) X-Gm-Message-State: AC+VfDz15SCHhQ3/MUo1oB5Juiahb/YE7Vix89LMLBAlbd+X4SnjygWz BiYBpfHQnWGfAMD1w9cuMmrAweSx1hZEqu9OwAw= X-Google-Smtp-Source: ACHHUZ4GuphcYeWZ1BQouSWnca/qnPzXRGri8ck9B48eMaGSD3ioHPyGYa+JhqCRjMXxtl/csyJ1nwQuptkQGyLdclQ= X-Received: by 2002:a17:903:32c8:b0:1ad:cba5:5505 with SMTP id i8-20020a17090332c800b001adcba55505mr16646873plr.14.1684838431165; Tue, 23 May 2023 03:40:31 -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: Sender: owner-freebsd-ports@freebsd.org X-BeenThere: freebsd-ports@freebsd.org MIME-Version: 1.0 References: <1623315797.5.1684837400228@mailrelay> In-Reply-To: <1623315797.5.1684837400228@mailrelay> From: Nuno Teixeira Date: Tue, 23 May 2023 11:40:19 +0100 X-Gmail-Original-Message-ID: Message-ID: Subject: Re: Improving www/chromium build time on arm64 To: Ronald Klop Cc: FreeBSD Mailing List , freebsd-arm@freebsd.org Content-Type: multipart/alternative; boundary="0000000000003196b105fc5a04b9" X-ThisMailContainsUnwantedMimeParts: N --0000000000003196b105fc5a04b9 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Hello Ronald, With your help I was able to find it in log. I'm building it again and I will upload log when it finished. Thanks! Ronald Klop escreveu no dia ter=C3=A7a, 23/05/2023 = =C3=A0(s) 11:23: > =C3=82 > > *Van:* Nuno Teixeira > *Datum:* dinsdag, 23 mei 2023 09:48 > *Aan:* FreeBSD Mailing List , > freebsd-arm@freebsd.org > *Onderwerp:* Re: Improving www/chromium build time on arm64 > > (...) > =C3=82 > But I also found that poudriere: > [88:53:28] Failed ports: www/chromium:build/timeout > =C3=82 > So I will search how do I increase build time to avoid timeout: > --- > # This defines the max time (in seconds) that a command may run for a bui= ld > # before it is killed for taking too long. Default: 86400 > #MAX_EXECUTION_TIME=3D86400 > --- > =C3=82 > I suspect it can be the cause of build failure because build >24h. > =C3=82 > Nuno Teixeira escreveu no dia ter=C3=83=C2=A7a, 23/= 05/2023 > =C3=83 (s) 08:31: > >> Hello all, >> =C3=82 >> I'm running 13-STABLE on rpi4 8 and since firefox{-esr} is constantly ta= b >> crashing and seg faulting I decided to give chromium a try. >> chromium pkg isn't available for arm64 and I didn't found error log at >> https://pkg-status.freebsd.org/ so I decided to build it on poudriere. >> =C3=82 >> It fails to build around 70% but my biggest concern is build time: 27 >> hours for 70% compilation! >> =C3=82 >> Just for comparison: >> llvm15: 12h >> rust: 9h >> firefox: 6h >> =C3=82 >> rip4 v1.5 8GB @ 2000Hz ~62 Celsius >> zfs >> poudriere: >> USE_TMPFS=3Dno >> PARALLEL_JOBS=3D1 >> ALLOW_MAKE_JOBS=3Dyes >> =C3=82 >> Any hints on how to speed build? ccache? >> Does cflags "-O -pipe" not present in compilation is related to build >> time? >> =C3=82 >> Full log: >> >> https://people.freebsd.org/~eduardo/logs/chromium/chromium-113.0.5672.12= 6.log >> =C3=82 >> Thanks! >> =C3=82 >> --- >> >> In file included from ../../base/check.h:11: >> ../../base/compiler_specific.h:8:10: fatal error: 'build/build_config.h' >> file not found >> #include "build/build_config.h" >> ^~~~~~~~~~~~~~~~~~~~~~ >> 1 error generated. >> ninja: build stopped: subcommand failed. >> =3D=3D=3D> Compilation failed unexpectedly. >> Try to set MAKE_JOBS_UNSAFE=3Dyes and rebuild before reporting the failu= re >> to >> the maintainer. >> *** Error code 1 >> >> Stop. >> make: stopped in /usr/ports/www/chromium >> build of www/chromium | chromium-113.0.5672.126 ended at Tue May 23 >> 02:22:56 WEST 2023 >> build time: 27:15:37 >> !!! build failure encountered !!! >> --- >> -- >> Nuno Teixeira >> FreeBSD Committer (ports) >> > > =C3=82 > -- > Nuno Teixeira > FreeBSD Committer (ports) > > > > Hi, > > My poudriere.conf for building ports on rpi4 contains these two changes: > > # This defines the max time (in seconds) that a command may run for a bui= ld > # before it is killed for taking too long. Default: 86400 > #MAX_EXECUTION_TIME=3D86400 > MAX_EXECUTION_TIME=3D172800 > > # This defines the time (in seconds) before a command is considered to > # be in a runaway state for having no output on stdout. Default: 7200 > #NOHANG_TIME=3D7200 > NOHANG_TIME=3D172800 > > > I'm maintaining some mongodb ports which also take a long long time to > build on rpi4. > But I don't remember which of these settings has the preferred impact on > your situation. > > Oh... now I'm reading your log better. It contains this: > "=3D>> Killing timed out build after 86400 seconds" > > And some time later: > "=3D>> Cleaning up wrkdir > =3D=3D=3D> Cleaning for chromium-113.0.5672.126" > > So the errors about missing files happen because poudriere is removing > files while some processes of the build are still running. > > I'm curious how far it gets after you increase MAX_EXECUTION_TIME. > > Regards, > Ronald. > =C3=82 > --=20 Nuno Teixeira FreeBSD Committer (ports) --0000000000003196b105fc5a04b9 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Hello Ronald,

With your help I was able= to find it in log.
I'm building it again and I will upload l= og when it finished.

Thanks!

Ronald Klop <= ronald-lists@klop.ws> escrev= eu no dia ter=C3=A7a, 23/05/2023 =C3=A0(s) 11:23:
=C3=82=C2=A0

Van: Nuno Teixeira <eduardo@freebsd.org>
Datum: dinsdag, 23 mei 2023 09:48
Aan: FreeBSD Mailing List <freebsd-ports@freebsd.org>, freebsd-arm@freebsd= .org
Onderwerp: Re: Improving www/chromium build time on arm64<= /p>

(...)
=C3=82=C2=A0
But I also found that poudriere:
[88:53:28] Failed ports: www/chromium:build/timeout
=C3=82=C2=A0
So I will search how do I increase build time to avoid timeout:
---
# This defines the max time (in seconds) that a command may run for a = build
# before it is killed for taking too long. Default: 86400
#MAX_EXECUTION_TIME=3D86400
---
=C3=82=C2=A0
I suspect it can be the cause of build failure because build >24h.<= /div>
=C3=82=C2=A0
Nuno Teixeira <eduardo@freebsd.org> escreveu no dia ter= =C3=83=C2=A7a, 23/05/2023 =C3=83=C2=A0(s) 08:31:
Hello all,
=C3=82=C2=A0
I'm running 13-STABLE on rpi4 8 and since firefox{-esr} is constan= tly tab crashing and seg faulting I decided to give chromium a try.
chromium pkg isn't available for arm64 and I didn't found erro= r log at=C2=A0https://pkg-status.freebsd.org/ so I decided to build it on poudriere.=
=C3=82=C2=A0
It fails to build around 70% but my biggest concern is build time: 27 = hours for 70% compilation!
=C3=82=C2=A0
Just for comparison:
llvm15: 12h
rust: 9h
firefox: 6h
=C3=82=C2=A0
rip4 v1.5 8GB @ 2000Hz ~62 Celsius
zfs
poudriere:
USE_TMPFS=3Dno
PARALLEL_JOBS=3D1
ALLOW_MAKE_JOBS=3Dyes
=C3=82=C2=A0
Any hints on how to speed build? ccache?
Does cflags "-O -pipe" not present in compilation is related= to build time?=C2=A0
=C3=82=C2=A0
Full log:
=C3=82=C2=A0
Thanks!
=C3=82=C2=A0
---
<SNIP>
In file included from ../../base/check.h:11:
../../base/compiler_specific.h:8:10: fatal error: 'build/build_config.h= ' file not found
#include "build/build_config.h"
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0^~~~~~~~~~~~~~~~~~~~~~
1 error generated.
ninja: build stopped: subcommand failed.
=3D=3D=3D> Compilation failed unexpectedly.
Try to set MAKE_JOBS_UNSAFE=3Dyes and rebuild before reporting the failure = to
the maintainer.
*** Error code 1

Stop.
make: stopped in /usr/ports/www/chromium
build of www/chromium | chromium-113.0.5672.126 ended at Tue May 23 02:22:5= 6 WEST 2023
build time: 27:15:37
!!! build failure encountered !!!
---
--
Nuno Teixeira
FreeBSD Committer (ports)
=C2=A0
=C3=82=C2=A0
--
Nuno Teixeira
FreeBSD Committer (ports)


Hi,

My poudriere.conf for building ports on rpi4 contains these two changes:
# This defines the max time (in seconds) that a command may run for a build=
# before it is killed for taking too long. Default: 86400
#MAX_EXECUTION_TIME=3D86400
MAX_EXECUTION_TIME=3D172800

# This defines the time (in seconds) before a command is considered to
# be in a runaway state for having no output on stdout. Default: 7200
#NOHANG_TIME=3D7200
NOHANG_TIME=3D172800


I'm maintaining some mongodb ports which also take a long long time to = build on rpi4.
But I don't remember which of these settings has the preferred impact o= n your situation.

Oh... now I'm reading your log better. It contains this:
"=3D>> Killing timed out build after 86400 seconds"

And some time later:
"=3D>> Cleaning up wrkdir
=3D=3D=3D> Cleaning for chromium-113.0.5672.126"

So the errors about missing files happen because poudriere is removing file= s while some processes of the build are still running.

I'm curious how far it gets after you increase MAX_EXECUTION_TIME.

Regards,
Ronald.
=C3=82=C2=A0


--
Nun= o Teixeira
FreeBSD Committer (ports)
--0000000000003196b105fc5a04b9--