Date: Wed, 30 Oct 2024 15:59:51 -0700 From: "Simon J. Gerraty" <sjg@juniper.net> To: Lexi Winter <lexi@le-fay.org> Cc: Larry Rosenman <ler@lerctr.org>, Freebsd current <freebsd-current@freebsd.org>, <sjg@juniper.net> Subject: Re: buildworld FAILURE:googletest Message-ID: <71560.1730329191@kaos.jnpr.net> In-Reply-To: <718c2958-0e2e-476a-bbc7-738b66a8124c@le-fay.org> References: <3defd95fd3c26a76cb5adf68977e30e1@lerctr.org> <8fc6573e8789a983517eb024949ec555@lerctr.org> <bd533ccb-43af-4a3f-bb09-bddc8ccd2163@le-fay.org> <55583.1730320961@kaos.jnpr.net> <718c2958-0e2e-476a-bbc7-738b66a8124c@le-fay.org>
next in thread | previous in thread | raw e-mail | index | archive | help
Lexi Winter <lexi@le-fay.org> wrote:
> > meta mode makes very little difference for a clean tree build,
> > it is only update builds where the .meta files become super useful.
>
> this was a build updating an existing obj tree from
>
> ~53314e34d5e8e7f781ab990805b22f7a56bc0580
>
> to
>
> ~22429a464a5f4f6bb5a056aae1353985db83b721
>
> so about 10 days worth of changes.
Ok so META_MODE should have been useful.
> > Though they are always good for build failure triage - helps if you have
> > MK_META_ERROR_TARGET=yes then you would get the failing .meta file(s)
> > copied to ERROR_LOGDIR which defaults to ${SRCTOP:H}/error/
>
> i will look at setting this in case it helps debug any future build issues.
If nothing else it eliminates the ambiguity.
If you have a error/meta*.log you *know* that is where your build
failed.
I ran a CI builder for about a decade, which about 90% of the time could
id the commit that broke the build. The above simplified its logic
considerably.
Of course you need to rotate error each time (should probably add that
to FreeBSD - contrib/bmake/mk/newlog.sh is used)
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?71560.1730329191>