Skip site navigation (1)Skip section navigation (2)
Date:      Tue, 22 Oct 2024 08:15:48 +0100
From:      Nuno Teixeira <eduardo@freebsd.org>
To:        current@freebsd.org, freebsd-current@freebsd.org
Subject:   Re: Build failure in share/examples/tests/tests/googletest/sample1_unittest.full
Message-ID:  <CAFDf7UJzf_4LMAbyctMsqUj-MA8-ALai%2BomccGo4h_%2BSGvAYLQ@mail.gmail.com>
In-Reply-To: <Zxa7G7KNAjRqJpio@albert.catwhisker.org>
References:  <ZxT0JVRwDUB_-eYD@albert.catwhisker.org> <ZxalWiMYJO-7zQva@int21h> <Zxa7G7KNAjRqJpio@albert.catwhisker.org>

index | next in thread | previous in thread | raw e-mail

[-- Attachment #1 --]
The only solution that I found was to delete /usr/obj/... and build from
scratch.

Cheers

David Wolfskill <david@catwhisker.org> escreveu (segunda, 21/10/2024 à(s)
21:36):

> On Mon, Oct 21, 2024 at 08:02:50PM +0100, void wrote:
> > On Sun, Oct 20, 2024 at 05:14:29AM -0700, David Wolfskill wrote:
> >
> > > This is in meta-mode, on a 32x2 Epyc running "make -j 112 buildworld".
> >
> > I'm just guessing here - but ISTR that with large -j that sometimes a
> build
> > failure can occur. I've just had one where I forgot where I was and ran
> a -j10
> > buildworld on a rpi4, and this failed halfway through.
> >
> > Now building with a much more reasonable -j4 ;)
> > ....
>
> FWIW, I had a recurrence of those errors on a couple of 4x2 machines
> running
> with -j 14.  And I really wouldn't want to be throttling a 32x2 machine
> down to -j 14.
>
> Peace,
> david
> --
> David H. Wolfskill                              david@catwhisker.org
> It has been said that history repeats itself. This is perhaps not quite
> correct; it merely rhymes. -- Theodor Reik
>
> See https://www.catwhisker.org/~david/publickey.gpg for my public key.
>


-- 
Nuno Teixeira
FreeBSD UNIX:  <eduardo@FreeBSD.org>   Web:  https://FreeBSD.org

[-- Attachment #2 --]
<div dir="ltr"><div>The only solution that I found was to delete /usr/obj/... and build from scratch.</div><div><br></div><div>Cheers<br></div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">David Wolfskill &lt;<a href="mailto:david@catwhisker.org">david@catwhisker.org</a>&gt; escreveu (segunda, 21/10/2024 à(s) 21:36):<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">On Mon, Oct 21, 2024 at 08:02:50PM +0100, void wrote:<br>
&gt; On Sun, Oct 20, 2024 at 05:14:29AM -0700, David Wolfskill wrote:<br>
&gt; <br>
&gt; &gt; This is in meta-mode, on a 32x2 Epyc running &quot;make -j 112 buildworld&quot;.<br>
&gt; <br>
&gt; I&#39;m just guessing here - but ISTR that with large -j that sometimes a build<br>
&gt; failure can occur. I&#39;ve just had one where I forgot where I was and ran a -j10<br>
&gt; buildworld on a rpi4, and this failed halfway through.<br>
&gt; <br>
&gt; Now building with a much more reasonable -j4 ;)<br>
&gt; ....<br>
<br>
FWIW, I had a recurrence of those errors on a couple of 4x2 machines running<br>
with -j 14.  And I really wouldn&#39;t want to be throttling a 32x2 machine<br>
down to -j 14.<br>
<br>
Peace,<br>
david<br>
-- <br>
David H. Wolfskill                              <a href="mailto:david@catwhisker.org" target="_blank">david@catwhisker.org</a><br>
It has been said that history repeats itself. This is perhaps not quite<br>
correct; it merely rhymes. -- Theodor Reik<br>
<br>
See <a href="https://www.catwhisker.org/~david/publickey.gpg" rel="noreferrer" target="_blank">https://www.catwhisker.org/~david/publickey.gpg</a>; for my public key.<br>
</blockquote></div><br clear="all"><br><span class="gmail_signature_prefix">-- </span><br><div dir="ltr" class="gmail_signature"><div dir="ltr"><div><font color="#888888">Nuno Teixeira</font></div><div><div><font color="#888888">
FreeBSD UNIX:  &lt;eduardo@FreeBSD.org&gt;   Web:  <a href="https://FreeBSD.org" rel="noreferrer" target="_blank">https://FreeBSD.org</a><br></font></div></div></div></div>;
home | help

Want to link to this message? Use this
URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAFDf7UJzf_4LMAbyctMsqUj-MA8-ALai%2BomccGo4h_%2BSGvAYLQ>