Re: error -9 on build cluster?

Dag-Erling_Smørgrav <des_at_FreeBSD.org> wrote on
Date: Fri, 30 May 2025 09:39:05 UTC :

> Ronald Klop <ronald-lists@klop.ws> writes:
> > My port databases/mongodb60 sometimes fails with an "error -9".
> > ports fallout: https://portsfallout.com/fallout?port=databases%2Fmongodb60%24
> > build report: https://lists.freebsd.org/archives/freebsd-pkg-fallout/2025-May/760518.html
> > full log (large): 
> > https://pkg-status.freebsd.org/beefy22/data/142amd64-default/a3de54ab2200/logs/mongodb60-6.0.23_1.log
> >
> > There is no output of the compiler which makes clear what happened. Only this output:
> >
> > scons: *** [build/59f4f0dd/mongo/db/catalog/multi_index_block.o] Error -9
> > scons: building terminated because of errors.
> > build/59f4f0dd/mongo/db/catalog/multi_index_block.o failed: Error -9
> > *** Error code 2
> 
> This is preceded by an 800-line list of warnings from a single source
> file (multi_index_block.cpp). This list is clearly truncated as it's
> missing the final “N warnings generated” line, so my guess is there is
> at least one error there as well which just doesn't get displayed.

My guess: the failure occurred while the warnings were otherwise
still being generated and that is what stopped the warnings.

> I
> would suggest trying to silence some of those warnings (maybe by adding
> -Wno-deprecated-builtins to CXXFLAGS).

Another interesting property is the history of the error occurring:

2025-Jan..Mar: 134arm64-default, main-arm64-default, and
141arm64-default were getting the error.

2025-Apr: 134arm64-quarterly started getting the failures.

2025-May: 142arm64-quarterly, main-amd64-default, and 142amd64-default
got the failure. (Note the mix of arm64 and amd64 here.)

See:

https://portsfallout.com/fallout?port=databases%2Fmongodb60&maintainer=&env=&category=&flavor=



Context note: With the pkg 2.1.0+ updates, build times on the
servers for 'bulk -C -a' like poudriere runs building port-packages
have been significantly increased. Avoid usual time frame assumptions,
arm64/armv7 (ampere* systems) having the largest change (main-arm64
is up to around 3 weeks for such a run now). The amperes also
cycle through sequence of different types on builds, not having
one server per type for aarch64/armv7. (So main-arm64 and main-armv7
each update only about once a month or longer now, for example.) Bapt
is working on improvements for the issue.

===
Mark Millard
marklmi at yahoo.com