From nobody Sat Sep 13 17:15:18 2025 X-Original-To: freebsd-current@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4cPHxY1wlvz67FZb for ; Sat, 13 Sep 2025 17:15:45 +0000 (UTC) (envelope-from brd@FreeBSD.org) Received: from smtp.freebsd.org (smtp.freebsd.org [96.47.72.83]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "smtp.freebsd.org", Issuer "R13" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4cPHxX6xkyz40Wl; Sat, 13 Sep 2025 17:15:44 +0000 (UTC) (envelope-from brd@FreeBSD.org) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=freebsd.org; s=dkim; t=1757783745; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: in-reply-to:in-reply-to:references:references; bh=aJB6wEEw+BSc7xUTcY7P0p8eUNZsUS45nweC7xioukw=; b=srDA/fmw/qNzK2QQkNUrxOJTvKOxV9JJaRb/GW1t5X2MGMEwIH9ftwIwb9LqbYZ9O2QUqJ iqT2KCB2R1WPksylJvD9Z2VXM5OHSMrxrFENs+TI5ifFFn/xe6kh5F59w3TuD/GRfY9ceO J85LER4UZzIy4f2BMbCuUbsFHT8m1x6JYjPS8obIatTc4GCnr0BNz5xjH298Z6qj07YjPJ aOCtcFbottDFOvSenlBt+EonFBWv/1ulW9PjBcdTswZudgIkdZf4bwzja8MR8PqSb4zF6y 0qHnMk+jf0ZlLZOEuoZ9PkbmaEo+gI7TDHIoxNG6czvSj6vUIkBuzW8ICXQV2g== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=freebsd.org; s=dkim; t=1757783745; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: in-reply-to:in-reply-to:references:references; bh=aJB6wEEw+BSc7xUTcY7P0p8eUNZsUS45nweC7xioukw=; b=QO5l5W9JX2RJrKIJaJtUKOvPlhrjOqElFYRBjRUHNW3vAHOrNtzgX/WXK0TlBBha0CTt+G eQe3bP+QNN5+IuucxPmeCDuH2nLSWxO/fZYPqe1N5r7pNEKxJuzKg8ZE5Js4NIVGl8Grjp EQYyiOOAvA+dWKbNVSKIq1nbvBh9i7ITY6ePoJiUg3nhqKRMikqtvGI9r8LZKCx6W2+/r1 0IuwZdyYBG++pOX7TMk6caGfkw28lYfNK3qzHTak5ODAb29PWIJ2veIDK7aiw4nuaTV39h SRJvVRerAwoCEzxLzsHSSwz1FCIQppboIY1aP7ybH2BApkFLDDYWxQlRL1xh7w== ARC-Seal: i=1; s=dkim; d=freebsd.org; t=1757783745; a=rsa-sha256; cv=none; b=i9DidUmw5bIwjF2IB1MF/86h0YNgc0hligrhJsUbGLUbxt8yfw/TeaUHq/DsgrHhOsVMwm 00lwaQ18rqpQj2DUg83f+ZmYskYrlNT3coUIxnc3esG4ezF20msZjgpVFT4zEGjKBS/jK5 FskUAzvKKV5wFgH7An29LJBjcOL3sOLmCUNZ4N6FlGFfjFuDg9MDzziGLZ+R9ohjgoM/ts 4uW8xZIaJWHKHHkePiydhGTdzLAGlSLqg4qgss/M8aIKfVEVXKFe2UbGX1G64ASWxzyjcX ZiaiwU37vsWclACB4uRFb2RSayAT8XWmDCPemknfW+3pm065YfUkg9Z32KsJ4w== ARC-Authentication-Results: i=1; mx1.freebsd.org; none Received: from fauth-a1-smtp.messagingengine.com (fauth-a1-smtp.messagingengine.com [103.168.172.200]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (Client did not present a certificate) (Authenticated sender: brd/mail) by smtp.freebsd.org (Postfix) with ESMTPSA id 4cPHxX5sLsz1M2p; Sat, 13 Sep 2025 17:15:44 +0000 (UTC) (envelope-from brd@FreeBSD.org) Received: from phl-compute-02.internal (phl-compute-02.internal [10.202.2.42]) by mailfauth.phl.internal (Postfix) with ESMTP id 14223F40076; Sat, 13 Sep 2025 13:15:40 -0400 (EDT) Received: from phl-imap-15 ([10.202.2.104]) by phl-compute-02.internal (MEProxy); Sat, 13 Sep 2025 13:15:40 -0400 X-ME-Sender: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgeeffedrtdeggdefvdehtdcutefuodetggdotefrod ftvfcurfhrohhfihhlvgemucfhrghsthforghilhdpuffrtefokffrpgfnqfghnecuuegr ihhlohhuthemuceftddtnecusecvtfgvtghiphhivghnthhsucdlqddutddtmdenucfjug hrpefoggffhffvvefkjghfufgtsegrtderreertdejnecuhfhrohhmpedfuehrrgguucff rghvihhsfdcuoegsrhgusefhrhgvvgeuufffrdhorhhgqeenucggtffrrghtthgvrhhnpe evjefgleevkeefveduheetgeelgeelvefguedvleduhfekgfelteehgeeiteehveenucff ohhmrghinhepihhntgdurdhithenucevlhhushhtvghrufhiiigvpedtnecurfgrrhgrmh epmhgrihhlfhhrohhmpegsrhgrugdomhgvshhmthhprghuthhhphgvrhhsohhnrghlihht hidqjedtjeeifedvfedvqddukedtieelieekkedqsghrugeppefhrhgvvgeuufffrdhorh hgsegsrhgruggurghvihhsrdhiohdpnhgspghrtghpthhtohepfedpmhhouggvpehsmhht phhouhhtpdhrtghpthhtohepihhmphessghsughimhhprdgtohhmpdhrtghpthhtohepfh hrvggvsghsugdqtghurhhrvghnthesfhhrvggvsghsugdrohhrghdprhgtphhtthhopehf sghsugesfiiffidriigvfhhogidrnhgvth X-ME-Proxy: Feedback-ID: if7394599:Fastmail Received: by mailuser.phl.internal (Postfix, from userid 501) id DC81078026F; Sat, 13 Sep 2025 13:15:39 -0400 (EDT) X-Mailer: MessagingEngine.com Webmail Interface List-Id: Discussions about the use of FreeBSD-current List-Archive: https://lists.freebsd.org/archives/freebsd-current List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-current@FreeBSD.org MIME-Version: 1.0 X-ThreadId: Au3vznxEFcdo Date: Sat, 13 Sep 2025 11:15:18 -0600 From: "Brad Davis" To: "Warner Losh" Cc: "bob prohaska" , "FreeBSD Current" Message-Id: <62cfbc85-6e12-4b00-90f8-8bd96a64dff5@app.fastmail.com> In-Reply-To: References: Subject: Re: Git and buildworld running at the same time Content-Type: multipart/alternative; boundary=5bd746853ab14d7a9f4355f98af62754 --5bd746853ab14d7a9f4355f98af62754 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable On Sat, Sep 13, 2025, at 10:06 AM, Warner Losh wrote: >=20 >=20 > On Sat, Sep 13, 2025 at 9:54=E2=80=AFAM Brad Davis w= rote: >> __ >> On Sat, Sep 13, 2025, at 9:40 AM, Warner Losh wrote: >>>=20 >>>=20 >>> On Sat, Sep 13, 2025 at 9:28=E2=80=AFAM Brad Davis = wrote: >>>> On Sat, Sep 13, 2025, at 8:57 AM, bob prohaska wrote: >>>> > Lately I've noticed that sometimes while running buildworld a top >>>> > window reports git running also. Up to now, I've surmised that >>>> > this is intentional, with git providing some housekeeping functio= n. >>>> > >>>> > Yesterday a buildworld session was accompanied by a prolonged >>>> > interval of git running also, with a large memory footprint, >>>> > near 1GB. That seems rather excessive. >>>> > >>>> > At the same time, it dawned on me that my recent habit has been >>>> > to run git pull, immediately followed by buildworld. Might it be >>>> > prudent to wait (how long?) to let git finish any housekeeping >>>> > triggered by the pull command? It seems likely that any overlap >>>> > could readily lead to inconsistencies which might account for >>>> > some of the buildworld problems I've been encountering lately. >>>>=20 >>>> This is part of the normal build process and how the output of unam= e -a includes bits like this: main-n280188-2024887abc7d-dirty or main-n2= 80188-2024887abc7d >>>>=20 >>>> To find out of the src tree is pristine or dirty the build process = uses git to find out. >>>=20 >>> Though that's only for the kernel, not for world builds. Right? >>=20 >> It happens for world builds as well.. newvers.sh runs git (used to be= svnlite) and is called in Makefile.inc1. >=20 > It doesn't need git for this: >=20 > # Set VERSION for CTFMERGE to use via the default CTFFLAGS=3D-L VERSIO= N. > .for _V in BRANCH REVISION TYPE > .if !defined(_${_V}) > ${_V}!=3D eval $$(awk '/^${_V}=3D/{print}' ${SRCTOP}/sys/conf/newvers= .sh); echo $$${_V} > .export _${_V} > .endif > .endfor >=20 > In fact, it's not even running newvers.sh, just using awk to grep out = these variables. Though it should be using newvers.sh -V here (which spe= cifically doesn't run git). Ooh, I see, good catch! Regards, Brad Davis --5bd746853ab14d7a9f4355f98af62754 Content-Type: text/html; charset=utf-8 Content-Transfer-Encoding: quoted-printable
On Sat, Sep = 13, 2025, at 10:06 AM, Warner Losh wrote:

<= br>
On Sat, Sep 13, 2025 at 9:54=E2=80=AFAM= Brad Davis <brd@freebsd.org&g= t; wrote:

On Sat, Sep 13, 2025, at = 9:40 AM, Warner Losh wrote:

On Sat, Sep 13, 2025 at 9:28=E2=80=AFAM Br= ad Davis <brd@fr= eebsd.org> wrote:
On Sat, Sep 13, 2025, at 8:57 AM, bob prohaska wrote:
> Lately I've noticed that sometimes while running buildworld a top=
> window reports git running also. Up to now, I've surmise= d that
> this is intentional, with git providing some house= keeping function.
>
> Yesterday a buildworld s= ession was accompanied by a prolonged
> interval of git run= ning also, with a large memory footprint,
> near 1GB. That = seems rather excessive.
>
> At the same time, = it dawned on me that my recent habit has been
> to run git = pull, immediately followed by buildworld. Might it be
> pru= dent to wait (how long?) to let git finish any housekeeping
&g= t; triggered by the pull command? It seems likely that any overlap
=
> could readily lead to inconsistencies which might account for<= /div>
> some of the buildworld problems I've been encountering la= tely.

This is part of the normal build process = and how the output of uname -a includes bits like this: main-n280188-202= 4887abc7d-dirty or main-n280188-2024887abc7d

To= find out of the src tree is pristine or dirty the build process uses gi= t to find out.

Though that's only = for the kernel, not for world builds. Right?

It happens for world builds as well.. newvers.sh = runs git (used to be svnlite) and is called in Makefile.inc1.

It doesn't need git for this:

# Set VERSION for CTFMERGE to use via the default = CTFFLAGS=3D-L VERSION.
.for _V in BRANCH REVISION TYPE
.if !defined(_${_V})
${_V}!=3D  eval $$(awk '/^${_V}=3D= /{print}' ${SRCTOP}/sys/conf/newvers.sh); echo $$${_V}
.export= _${_V}
.endif
.endfor

In fact, it's not even running newvers.sh, just using awk to grep out = these variables. Though it should be using newvers.sh -V here (which spe= cifically doesn't run git).

Ooh, I see, good catch!


Re= gards,
Brad Davis

--5bd746853ab14d7a9f4355f98af62754--