Van: Mark Millard <[email protected]>
Datum:vrijdag, 30 mei 2025 20:58
Aan:"Dag-Erling Smørgrav" <[email protected]>
CC:[email protected], FreeBSD Mailing List <[email protected]>
Onderwerp:Re: error -9 on build cluster?

On May 30, 2025, at 11:29, Mark Millard <[email protected]> wrote:

> On May 30, 2025, at 10:43, Dag-Erling Smørgrav <[email protected]> wrote:
>
>> Mark Millard <[email protected]> writes:
>>> Dag-Erling Smørgrav <[email protected]> writes:
>>>> 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.
>>
>> That's possible.  If we assume that the error code returned by scons is
>> an errno, it corresponds to EBADF.  Perhaps a bug in scons causes it to
>> lose track of the pipe it uses to read the compiler's stderr.
>
> devel/scans has not been updated after 2024-Jun-06:
>
> QUOTE
> author Po-Chuan Hsieh <[email protected]> 2024-06-06 22:03:56 +0000
> committer Po-Chuan Hsieh <[email protected]> 2024-06-06 22:03:56 +0000
> . . .
> devel/scons: Update to 4.7.0
> Changes: https://github.com/SCons/scons/releases 
https://scons.org/tag/releases.html PR: 279488 Exp-run by: antoine
> END QUOTE
>
> That would mean that quarterly got the update in 2024 as well.
>
> 
https://pkg-status.freebsd.org/ampere1/data/141arm64-quarterly/2e2d801cf977/logs/mongodb60-6.0.18.log
>
> did not fail but shows the warnings.
>
> devel/scons does not seem to be the source of the change in beavior.


Worked:

https://pkg-status.freebsd.org/ampere3/data/134arm64-default/1afdc808e67b/logs/mongodb60-6.0.20_1.log
build started at Sun Jan  5 17:35:49 UTC 2025

The next 134arm64-default build Failed:

https://pkg-status.freebsd.org/ampere3/data/134arm64-default/86e28c84a7e0/logs/errors/mongodb60-6.0.20_1.log
build started at Sun Jan 19 11:21:16 UTC 2025

That at least  gives a time frame to investigate.

More details:

=>> Building databases/mongodb60
build started at Sun Jan  5 17:35:49 UTC 2025
port directory: /usr/ports/databases/mongodb60
package name: mongodb60-6.0.20_1
building for: FreeBSD 134arm64-default-job-06 13.4-RELEASE-p2 FreeBSD 
13.4-RELEASE-p2 arm64
maintained by: [email protected]
Makefile datestamp: -rw-r--r--  1 root  wheel  5845 Jan  4 01:02 
/usr/ports/databases/mongodb60/Makefile
Ports top last git commit: 1afdc808e67
Ports top unclean checkout: no
Port dir last git commit: 3ab18c284b0
Port dir unclean checkout: no
Poudriere version: poudriere-git-3.4.2
Host OSVERSION: 1500028
Jail OSVERSION: 1304000

vs.

=>> Building databases/mongodb60
build started at Sun Jan 19 11:21:16 UTC 2025
port directory: /usr/ports/databases/mongodb60
package name: mongodb60-6.0.20_1
building for: FreeBSD 134arm64-default-job-13 13.4-RELEASE-p2 FreeBSD 
13.4-RELEASE-p2 arm64
maintained by: [email protected]
Makefile datestamp: -rw-r--r--  1 root  wheel  5845 Jan  4 01:02 
/usr/ports/databases/mongodb60/Makefile
Ports top last git commit: 86e28c84a7e
Ports top unclean checkout: no
Port dir last git commit: 3ab18c284b0
Port dir unclean checkout: no
Poudriere version: poudriere-git-3.4.2
Host OSVERSION: 1500028
Jail OSVERSION: 1304000

Same Host and Jail OSVERSION's. Same "Port dir last git commit".

But different "Ports top last git commit". So. some change in
another package that is involved?

===
Mark Millard
marklmi at yahoo.com





Hi,

The builder got the same error on mongodb70. But this build does not have all 
the warnings. I still don't see the cause of Error -9.

https://pkg-status.freebsd.org/beefy22/data/142amd64-default/02e9dc3b903b/logs/mongodb70-7.0.21_1.log

https://portsfallout.com/fallout?port=databases%2Fmongodb70%24

My next idea is that this occurs because a process gets killed (-9), which 
should be visible in the logs of the cluster maintainers. Does this makes sense?

Regards,
Ronald.

Reply via email to