From nobody Tue May 23 10:23:20 2023 X-Original-To: freebsd-arm@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 4QQVlP0389z4CJPn; Tue, 23 May 2023 10:23:29 +0000 (UTC) (envelope-from SRS0=QxZD=BM=klop.ws=ronald-lists@realworks.nl) Received: from smtp-relay-int.realworks.nl (smtp-relay-int.realworks.nl [194.109.157.24]) (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 did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 4QQVlN4ZD2z3G5C; Tue, 23 May 2023 10:23:28 +0000 (UTC) (envelope-from SRS0=QxZD=BM=klop.ws=ronald-lists@realworks.nl) Authentication-Results: mx1.freebsd.org; none Date: Tue, 23 May 2023 12:23:20 +0200 (CEST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=klop.ws; s=rw2; t=1684837400; 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=w8uZFf+Eg6AW6Fu5inKfkqq45tQYNbK7cKzKAzj2Xvw=; b=o7dgn2j6wO/NSr5XHDBPbFJ9xELnptIpXXZZ2MufgHVnR7gwMO+wwHd7tlBcgoSq5VeqRM 0WmnMsGyfNeVIlLShYbq77yYewluNDaOmhDgtLUBdYbAP+ndjoaL/iQVb0+7b5SJYTwNnS +hrHJT3EZy+hGi4NpLX1PU9aqZNDw6Tp0SHCfh3+fXEXgHmaBwnvY0HOhHbaEwhkS1mpVM 5dWE4nT479HI3bmR17bptjpqBjq8pyxk+hycXkFoInOZ7ChDYQqd9/zaoj2AOgsHlDnhfq AOOqVgyJff0QF/+dE6MFpInaxD4+tTlEDTcsFAbK2nEZXKkvxrJ0eZMi62J1Dw== From: Ronald Klop To: Nuno Teixeira Cc: FreeBSD Mailing List , freebsd-arm@freebsd.org Message-ID: <1623315797.5.1684837400228@mailrelay> In-Reply-To: References: Subject: Re: Improving www/chromium build time on arm64 List-Id: Porting FreeBSD to ARM processors List-Archive: https://lists.freebsd.org/archives/freebsd-arm List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-arm@freebsd.org MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_Part_4_278167197.1684837399175" X-Mailer: Realworks (655.324) Importance: Normal X-Priority: 3 (Normal) X-Rspamd-Queue-Id: 4QQVlN4ZD2z3G5C X-Spamd-Bar: ---- X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[]; ASN(0.00)[asn:3265, ipnet:194.109.0.0/16, country:NL] X-Rspamd-Pre-Result: action=no action; module=replies; Message is reply to one we originated X-ThisMailContainsUnwantedMimeParts: N ------=_Part_4_278167197.1684837399175 Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: quoted-printable =C3=82=20 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 >=20 > (...) > =C3=82=20 > But I also found that poudriere: > [88:53:28] Failed ports: www/chromium:build/timeout > =C3=82=20 > 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=20 > I suspect it can be the cause of build failure because build >24h. > =C3=82=20 > Nuno Teixeira escreveu no dia ter=C3=83=C2=A7a, 23/= 05/2023 =C3=83 (s) 08:31: >>=20 >> Hello all, >> =C3=82=20 >> 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 h= ttps://pkg-status.freebsd.org/ so I decided to build it on poudriere. >> =C3=82=20 >> It fails to build around 70% but my biggest concern is build time: 27 ho= urs for 70% compilation! >> =C3=82=20 >> Just for comparison: >> llvm15: 12h >> rust: 9h >> firefox: 6h >> =C3=82=20 >> rip4 v1.5 8GB @ 2000Hz ~62 Celsius >> zfs >> poudriere: >> USE_TMPFS=3Dno >> PARALLEL_JOBS=3D1 >> ALLOW_MAKE_JOBS=3Dyes >> =C3=82=20 >> Any hints on how to speed build? ccache? >> Does cflags "-O -pipe" not present in compilation is related to build ti= me?=20 >> =C3=82=20 >> Full log: >> https://people.freebsd.org/~eduardo/logs/chromium/chromium-113.0.5672.12= 6.log >> =C3=82=20 >> Thanks! >> =C3=82=20 >> --- >> >> 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 >>=20 >> Stop. >> make: stopped in /usr/ports/www/chromium >> build of www/chromium | chromium-113.0.5672.126 ended at Tue May 23 02:2= 2:56 WEST 2023 >> build time: 27:15:37 >> !!! build failure encountered !!! >> --- >> --=20 >> Nuno Teixeira >> FreeBSD Committer (ports) >=20 > =20 > =C3=82=20 > --=20 > 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 buil= d on rpi4. But I don't remember which of these settings has the preferred impact on yo= ur 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=20 ------=_Part_4_278167197.1684837399175 Content-Type: text/html; charset=utf-8 Content-Transfer-Encoding: quoted-printable =C3=82 

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 
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 = build
# 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.<= /div>
=C3=82 
Nuno Teixeira <eduardo@freebsd.org> 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 = tab 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:
=C3=82 
Thanks!
=C3=82 
---
<SNIP>
In file included from ../../base/check.h:11:
../../base/compiler_specific.h:8:10: fatal error: 'build/build_config.h' fi= le 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 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)
 
=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 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 buil= d on rpi4.
But I don't remember which of these settings has the preferred impact on yo= ur 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  ------=_Part_4_278167197.1684837399175--