From nobody Sat Sep 13 15:40:12 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 4cPFqf0cMYz66dVt for ; Sat, 13 Sep 2025 15:40:30 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: from mail-pj1-x102e.google.com (mail-pj1-x102e.google.com [IPv6:2607:f8b0:4864:20::102e]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "smtp.gmail.com", Issuer "WR4" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4cPFqd5X8Fz3gJM for ; Sat, 13 Sep 2025 15:40:29 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Authentication-Results: mx1.freebsd.org; none Received: by mail-pj1-x102e.google.com with SMTP id 98e67ed59e1d1-32dc6616f7dso2209966a91.1 for ; Sat, 13 Sep 2025 08:40:29 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=bsdimp-com.20230601.gappssmtp.com; s=20230601; t=1757778023; x=1758382823; darn=freebsd.org; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=I9V1kWEO8bfw6txhIy0Rq/UsnYawFsun24h03seSuDA=; b=BXeGwxpAB/XXfnigoHdhgIxnhvOLjktfIpdnbqSa6jKFxJJXOc+ugk5Az341+r5Hjj Ya0y46gfEOPLj1yBSP7WHYEIub4D82oM5H2EQac7KhvYbSXYuxKHYSY17nKNP+I18KDk ipz7KmlvR5paa7GGTXsGczNlAG/mdFtpoic7aJKIB7ezSc1QhceKXhTJH9FEhAFhPw66 t5PEEDBncDCqMn3fMfMXkhhNBQ18xafsJKulvqkf136Q5wc0Cyz4OJrwOrXvybMQ0bjD hplX3FjcP8wXhfcXP7KW/+Wrn4mg9L2Wj9ZemxXVJ+VPhwoLOiJ+EI5d79sWiSx5gTUG wXfQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1757778023; x=1758382823; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=I9V1kWEO8bfw6txhIy0Rq/UsnYawFsun24h03seSuDA=; b=SJn5Zbl6wwAUTdicsQUg0sH3gEMxLdLkmWighKVKA6WOpQrNs/+KSCMjqc3e1ztikJ 2+r1M4gAtSfA6Ks7Wiwo89MdC2y4s8WVBdYImYBrcP7YPs33EuAXYUTIGwiXShI0T0as uY6qlra1rHKOAqYGNcU9pcBu7vAYLV4abylDjtuymeI76FnSUexkIUus+qpgfMGnrSPe KhbqimF/E1iDOlKKTrSiGEr3Fi8QeJWjQp6Jbs/UcoEOwHcEA0tppFGUs423JDz1MiiB ABTCvfpNIfuIELK5U2CUEIv7CFr0gFD5QshxBnS6d7/vh7oBHGsToJ8DumYkaLiEzSK6 otwg== X-Forwarded-Encrypted: i=1; AJvYcCVVXo2FVVDVV+nu0PsN+wKncWiC/V5zbFzgzscoGV3CXePma9OaXODgxP9voMuzZJADVd7HbRgDylMn2Wh1zKA=@freebsd.org X-Gm-Message-State: AOJu0YzZ5Wv2pNriN2YLVwsqc/hblChl6SF4RBgdpgYqfVbdAQ2eIQMZ EDnyf1kxPUXviU8omelNAR53JkrystB/m13WEs7GLbK6u2K09MMHreQVUFaXE815vtio9rSnUoW KwcQGNzY5hEFeQsMw/t8C5EQ0jn/HCp1ZPQpBPxJufgp1woh/z9Jsypk= X-Gm-Gg: ASbGnctZ89a1dhuSW/JJlopUqJhbDZn/8wnLUqz8bRM32MUua9T/TCG/SBzH1+LqSP7 alpneD3lu/EQdMhTUSBgR63hzQVI3N7WFWijM45p98YZSz5Ek+GZ2ceYaE0ajsvTe0LsY+dLSya r18VPtQBaXhhPpOheG74QImB+oC6/SFjW6iXTk+QNymRZb+/wqwVcb07eSebmirR5Hns+X/q5R7 Ms9ROFZNbqpBmma81jp3L8/6DK++jCZb6sl9aXs64qIhznrCw== X-Google-Smtp-Source: AGHT+IHxLP5sRCTJwFdplpIH+qbThuOsLlhq3wvgBlj68nlYaOUtFp3eMfIRlDejbqzROw5pRlB2d/pI+BacBkchw2Q= X-Received: by 2002:a17:90b:4c85:b0:32b:ab04:291e with SMTP id 98e67ed59e1d1-32de4f9611dmr7944397a91.25.1757778023522; Sat, 13 Sep 2025 08:40:23 -0700 (PDT) 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 References: In-Reply-To: From: Warner Losh Date: Sat, 13 Sep 2025 09:40:12 -0600 X-Gm-Features: Ac12FXyf3_Ekz8olgi4KA9ZfMyUZvr20ymajdqXVlsqI51sxaMgxiycQZrj1hds Message-ID: Subject: Re: Git and buildworld running at the same time To: Brad Davis Cc: bob prohaska , FreeBSD Current Content-Type: multipart/alternative; boundary="000000000000afb704063eb0968f" X-Spamd-Bar: ---- X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[]; ASN(0.00)[asn:15169, ipnet:2607:f8b0::/32, country:US] X-Rspamd-Pre-Result: action=no action; module=replies; Message is reply to one we originated X-Rspamd-Queue-Id: 4cPFqd5X8Fz3gJM --000000000000afb704063eb0968f Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable 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 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. > > 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-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? Warner --000000000000afb704063eb0968f Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable


On Sat, Sep 13,= 2025 at 9:28=E2=80=AFAM Brad 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 buildworld a top<= br> > window reports git running also. Up to now, I've surmised that > 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.

This is part of the normal build process and how the output of uname -a inc= ludes bits like this: main-n280188-2024887abc7d-dirty or main-n280188-20248= 87abc7d

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

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

Warner<= /div>
--000000000000afb704063eb0968f--