Re: Improving www/chromium build time on arm64

On May 23, 2023, at 03:23, Ronald Klop <ronald-lists@klop.ws> wrote:

> . . .
> 
> 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=86400
> MAX_EXECUTION_TIME=172800
> 
> # 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=7200
> NOHANG_TIME=172800
> 
> 
> 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.
> 
> . . .

FYI:

There are some ports that do not generate periodic output
while they take a long time building. For them, when
NOHANG_TIME < MAX_EXECUTION_TIME , NOHANG_TIME ends up
being what stops them.

Thus, if one wants to build any examples of such ports,
setting NOHANG_TIME to the same value as MAX_EXECUTION_TIME
can be appropriate. It does trade off earlier detection of
hangups for ports that do have periodic output. Another
form of monitoring can be appropriate because of this.


===
Mark Millard
marklmi at yahoo.com