From nobody Sat Sep 13 16:06:27 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 4cPGPs17GKz66g9G for ; Sat, 13 Sep 2025 16:06:41 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: from mail-pj1-x102d.google.com (mail-pj1-x102d.google.com [IPv6:2607:f8b0:4864:20::102d]) (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 4cPGPr6D4Lz3mcF for ; Sat, 13 Sep 2025 16:06:40 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Authentication-Results: mx1.freebsd.org; none Received: by mail-pj1-x102d.google.com with SMTP id 98e67ed59e1d1-323266cdf64so2518404a91.0 for ; Sat, 13 Sep 2025 09:06:40 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=bsdimp-com.20230601.gappssmtp.com; s=20230601; t=1757779599; x=1758384399; 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=yF60GmoUjNvHivniTZHU5ZcJyxbciD+Twbks7ZZSS18=; b=sjegHvWYCJ46UTBT04uByZdVW/yyPBVldQksf9N0y3usCxD0mUAURBBzemg7hLxSRl KrL4ym8v3d3ktUClkqqqVgTW28cXhTTDpgTFRtJkAs0VmycZSSe7q8Z+xTCj+K2tDH2v SNeqZUACPCfCDc/86MyySDsK1ES92uf7ZIGvlVHz6eQoC9xOno8xXucZxgLxuiiMDUUl TrTajzaDYhzjTCNeUvCHU/2wlEOGSfl/QR6visjASnhAzIRQZ30Nr+k/UzRPyq/dw9I/ xIazBfyVAdKrH5A4mYYDrnoEHdIdBUYGz3reBbKPHI7/ovCWVlQW9NeRsmgYSSoGleJd /xMQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1757779599; x=1758384399; 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=yF60GmoUjNvHivniTZHU5ZcJyxbciD+Twbks7ZZSS18=; b=jCLnLPBSZy5r3N1NBtEm5qCfijILyYvja8ZjWgs0d3Tb+3kVTMuxz+/wu3p8UkdFqv uxYbt2aQtenTvgBcajWsrUZOkZydMo04GIhCM5rQFLWyk2NC6HIoWI5jcPHSPmiT2063 ptV3fS8MqjKHTRSuh2k4keqtXyvGGn5JAS988Ndqo3chv1nvgGiT4wQg5zv8mQHji9bg y/n53Szp1zbEfXM8OBSSkmZ+R7Hu7QWH5GGiWGptVJG5Mt8Ph6jYp7r8IwmJygArDOZR zMxDRvPPtY4o6GJOP8WKhdhdzwrhW16LoGvQFEmo/EwkcXThbD6LK+lxmmolTFbDw440 MQKQ== X-Forwarded-Encrypted: i=1; AJvYcCX0UH4Pq13vOtmT02CwV0ZzzNSsZi0/EuN3i9NpqsXOx4Sku/uwEKOM+FXf6OuMfVlSeStdiefY+oRMVuML4Uw=@freebsd.org X-Gm-Message-State: AOJu0YzOqWH99hbTI7h1tZmXm6i4D0aH+AH7ntLqB7xyNIQwVsnx9NVb Lt+mpQFHg/VChTOLx4vGFCeVy9rEI53It8n+RMxzVhX3Sewm3FZsdGoouZbZb93LRAtBb8PqS+4 01mICHPQZ1GojRvECNZtyCTBlCMhvP3ZArQQNzyWbb7t6RIsfyry4eGwzxA== X-Gm-Gg: ASbGncvXUPOlfcitA6PLcxkQtUOwKGVJFU/t7UxlSk7dwhXhcyNF/RJoL8ov1B0UtyG lvj0DxCsDD9QXxyomiDFQUqxlhHr3Q48n+/CPj+TNT9E9xUphpqEh5CdWToeQpPuwLW1C4aS7IP kXrwdf0cdniRZTuu0xzEFcFRt6AUv84li4WKvP89njZWIlUwy+Gf4lwh2MEbkfp2CQXFDh84eE1 OOhjL/xJsqYSbSeASE4zF81mqizK130X4VF1Gf/x8q7mxAa0w== X-Google-Smtp-Source: AGHT+IF/mUf/p1PWcCjNmMHRNKZjMidlVhtA7U5w8HGtFObI6lsaD3S+gYBAlsSjvQNBPPAt2YgmN7tBdS0meb1HnQ4= X-Received: by 2002:a17:90b:3901:b0:327:ba77:a47 with SMTP id 98e67ed59e1d1-32de4f97d10mr8329035a91.15.1757779598546; Sat, 13 Sep 2025 09:06:38 -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 10:06:27 -0600 X-Gm-Features: Ac12FXxa9LPZNqSnocLgbvh_zxwAqSgs4BF7ReBUI-kNfNTFh7OSucvbt-gEdmQ 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="00000000000090af5c063eb0f4d1" 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: 4cPGPr6D4Lz3mcF --00000000000090af5c063eb0f4d1 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable On Sat, Sep 13, 2025 at 9:54=E2=80=AFAM Brad Davis wrote: > On Sat, Sep 13, 2025, at 9:40 AM, Warner Losh wrote: > > > > On Sat, Sep 13, 2025 at 9:28=E2=80=AFAM Brad Davis wrot= e: > > 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? > > > 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 specifically doesn't run git). So what else is running it behind the scenes? Warner > > > Regards, > Brad Davis > > > --00000000000090af5c063eb0f4d1 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable


On Sat, Sep 13,= 2025 at 9:54=E2=80=AFAM Brad Davis <= brd@freebsd.org> wrote:
On Sat, Sep 13, 2025, at 9:40 AM, Warner Lo= sh wrote:


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 prohask= a wrote:
> Lately I've noticed that sometimes while runni= ng buildworld a top
> window reports git running also. Up to = now, I've surmised that
> this is intentional, with git = providing some housekeeping function.
>
> Yeste= rday a buildworld session was accompanied by a prolonged
> in= terval of git running also, with a large memory footprint,
> = near 1GB. That seems rather excessive.
>
> At t= he 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<= /div>
> could readily lead to inconsistencies which might account f= or
> some of the buildworld problems I've been encounteri= ng lately.

This is part of the normal build proc= ess and how the output of uname -a includes bits like this: main-n280188-20= 24887abc7d-dirty or main-n280188-2024887abc7d

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

Though that's only fo= r 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 VERS= ION.
.for _V in BRANCH REVISION TYPE
.if !defined(_${_V})
${_V}!= =3D =C2=A0eval $$(awk '/^${_V}=3D/{print}' ${SRCTOP}/sys/conf/newve= rs.sh); echo $$${_V}
.export _${_V}
.endif
.endfor

<= /div>
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 (whi= ch specifically doesn't run git).

So what else= is running it behind the scenes?

Warner


=
Regards,
Brad Davis


--00000000000090af5c063eb0f4d1--