From nobody Sat Sep 13 15:53:46 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 4cPG7M0Lyzz66f5H for ; Sat, 13 Sep 2025 15:54:07 +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 4cPG7L6y1tz3kvw; Sat, 13 Sep 2025 15:54:06 +0000 (UTC) (envelope-from brd@FreeBSD.org) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=freebsd.org; s=dkim; t=1757778847; 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=qhAJpDWF7s/nJKP8oQTPitsuCeZ/sLLVRKJL5PVVI1U=; b=h3oJLJ1tg6X9hbSY5guz0JgiMIS2jtxS8RCJyekILR8DFjnDfhKE8+ZzRhAGgdeXFBLZgX AuBg4HTo1KfFYGAiTBigV7vvtoNFaHcbMcG66rc82ny95wVWh7R3yE3na8hodUqHb2zojk pKpiiOpbVUVQeHx+EEhNs5ssB8uYz/U9hlNU5rCKJb4JtqsRC3rAlLcX7KC6pPlgoSxlpY NXal3+JUKb4jcN3QYbfwvouOj9ldaHf5X+WyXYPn8bVlj+zHV2RAmqr5Tm8nRvomwMrlyn fqo7KxET1EqS+XvLT3j5YUIe/kdXkM1KZnpRWZN5dSLoKRh5mjcG0iXRCVXW6w== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=freebsd.org; s=dkim; t=1757778847; 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=qhAJpDWF7s/nJKP8oQTPitsuCeZ/sLLVRKJL5PVVI1U=; b=nb9XpDh8PmCzfM09GdjvYFf6EaGU0mnQyikLNHr2FnSIl88kCSQUnu085q4OD1AqiO9Xvn e+ylXXUjk+w3nQFZ+/+muVA0l/HTxUQOwVtCE9IvbXNHaRXwGGlHBRi+/VLummj9svo5nj sKw2ok/OFNSGpXWjrCNvpoG3RA/TdaAd2O4LErwieKxIaxOyXI5N9shVMjxVSznOi1XNpn 6Q6Xi/gJvza6EM9XtPagrRw1/wBNOHLT2mxg2qfy3dgvo6wUtgffyZUO3w8s6BjQOwqxxu 39uvGyltP0Tu0ECVG38PlEZq2VUCseYzE8sEvni5ehIeNqp37UAJKB/DuShG4Q== ARC-Seal: i=1; s=dkim; d=freebsd.org; t=1757778847; a=rsa-sha256; cv=none; b=bH/FS9ruRptWHRaTjWoUUKz6+ARd4wLE4fe5tu/TCRuhuZxkRYhPNS+wOLNKA7Ml0ZEed/ LclHQrYZwmHE3wyUA3VNZLDCV9nCNkSFOVIdDqkYIAUcy6pZ9uWl8HuLOKOKZm2UW4gn28 iaNQMKRwH+z3KW0vtPDfOYCKuWtDlyvySf6I85MYNXkQ+Yub5RhJpAmvUj35Fko+p4Au+Z S80B/GA0hSXDQfsHojS/yzPPf2MK0RikaxA4M+7E8JMFnjf2QRUk76c6F7YDlpf/fA2Sqr +mUbvKfmalO5YHzwXq3dWgm3wSdSvotFwz6rfV/rZAfcPOEQ6wwlPS8WTnXAig== ARC-Authentication-Results: i=1; mx1.freebsd.org; none Received: from fauth-a2-smtp.messagingengine.com (fauth-a2-smtp.messagingengine.com [103.168.172.201]) (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 4cPG7L65nRz1Kg4; Sat, 13 Sep 2025 15:54:06 +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 B26E3F4006E; Sat, 13 Sep 2025 11:54:06 -0400 (EDT) Received: from phl-imap-15 ([10.202.2.104]) by phl-compute-02.internal (MEProxy); Sat, 13 Sep 2025 11:54:06 -0400 X-ME-Sender: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgeeffedrtdeggdefvdefgecutefuodetggdotefrod ftvfcurfhrohhfihhlvgemucfhrghsthforghilhdpuffrtefokffrpgfnqfghnecuuegr ihhlohhuthemuceftddtnecusecvtfgvtghiphhivghnthhsucdlqddutddtmdenucfjug hrpefoggffhffvvefkjghfufgtsegrtderreertdejnecuhfhrohhmpedfuehrrgguucff rghvihhsfdcuoegsrhgusefhrhgvvgeuufffrdhorhhgqeenucggtffrrghtthgvrhhnpe dufffgvedufeejheehtdetjedthfehjefgjeetheelfeelleegieduleffheduhfenucev lhhushhtvghrufhiiigvpedtnecurfgrrhgrmhepmhgrihhlfhhrohhmpegsrhgrugdomh gvshhmthhprghuthhhphgvrhhsohhnrghlihhthidqjedtjeeifedvfedvqddukedtieel ieekkedqsghrugeppefhrhgvvgeuufffrdhorhhgsegsrhgruggurghvihhsrdhiohdpnh gspghrtghpthhtohepfedpmhhouggvpehsmhhtphhouhhtpdhrtghpthhtohepihhmphes sghsughimhhprdgtohhmpdhrtghpthhtohepfhhrvggvsghsugdqtghurhhrvghnthesfh hrvggvsghsugdrohhrghdprhgtphhtthhopehfsghsugesfiiffidriigvfhhogidrnhgv th X-ME-Proxy: Feedback-ID: if7394599:Fastmail Received: by mailuser.phl.internal (Postfix, from userid 501) id 8942378026F; Sat, 13 Sep 2025 11:54:06 -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 09:53:46 -0600 From: "Brad Davis" To: "Warner Losh" Cc: "bob prohaska" , "FreeBSD Current" Message-Id: In-Reply-To: References: Subject: Re: Git and buildworld running at the same time Content-Type: multipart/alternative; boundary=a8381887fa904e7fb94f44b2546598e9 --a8381887fa904e7fb94f44b2546598e9 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable 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 w= rote: >> 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=20 >> > this is intentional, with git providing some housekeeping function. >> > >> > 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 uname = -a includes bits like this: main-n280188-2024887abc7d-dirty or main-n280= 188-2024887abc7d >>=20 >> To find out of the src tree is pristine or dirty the build process us= es git to find out. >=20 > 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 sv= nlite) and is called in Makefile.inc1. Regards, Brad Davis --a8381887fa904e7fb94f44b2546598e9 Content-Type: text/html; charset=utf-8 Content-Transfer-Encoding: quoted-printable
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@freebsd.org> = wrote:
On Sat, Sep 13, 2025, at 8:57 AM, bob prohaska wrote:
> Lately I've noticed that sometimes while running buildwor= ld a top
> window reports git running also. Up to now, I'v= e surmised that
> this is intentional, with git providing= some housekeeping function.
>
> Yesterday a= buildworld session was accompanied by a prolonged
> inter= val of git running also, with a large memory footprint,
> = near 1GB. That seems rather excessive.
>
> A= t the same time, it dawned on me that my recent habit has been
> to run git pull, immediately followed by buildworld. Might it be<= /div>
> prudent to wait (how long?) to let git finish any housek= eeping
> triggered by the pull command? It seems likely th= at any overlap
> could readily lead to inconsistencies whi= ch might account for
> some of the buildworld problems I'v= e been encountering lately.

This is part of t= he normal build process and how the output of uname -a includes bits lik= e this: main-n280188-2024887abc7d-dirty or main-n280188-2024887abc7d

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

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

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


Regards,
Brad Davis


--a8381887fa904e7fb94f44b2546598e9--