Date: Sat, 13 Sep 2025 09:40:12 -0600 From: Warner Losh <imp@bsdimp.com> To: Brad Davis <brd@freebsd.org> Cc: bob prohaska <fbsd@www.zefox.net>, FreeBSD Current <freebsd-current@freebsd.org> Subject: Re: Git and buildworld running at the same time Message-ID: <CANCZdfrNw=AHLUcKxGzYoPQ7Zs=E2Wjp6Kqq4E3aU_LyBh_snA@mail.gmail.com> In-Reply-To: <f9ae18ca-13d9-4fdc-8ee4-6b1870ad67ad@app.fastmail.com> References: <aMWGWbI-8TwnAPnP@www.zefox.net> <f9ae18ca-13d9-4fdc-8ee4-6b1870ad67ad@app.fastmail.com>
index | next in thread | previous in thread | raw e-mail
[-- Attachment #1 --] On Sat, Sep 13, 2025 at 9:28 AM 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 > > 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 [-- Attachment #2 --] <div dir="ltr"><div dir="ltr"><br></div><br><div class="gmail_quote gmail_quote_container"><div dir="ltr" class="gmail_attr">On Sat, Sep 13, 2025 at 9:28 AM Brad Davis <<a href="mailto:brd@freebsd.org">brd@freebsd.org</a>> wrote:<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 Sat, Sep 13, 2025, at 8:57 AM, bob prohaska wrote:<br> > Lately I've noticed that sometimes while running buildworld a top<br> > window reports git running also. Up to now, I've surmised that <br> > this is intentional, with git providing some housekeeping function.<br> ><br> > Yesterday a buildworld session was accompanied by a prolonged<br> > interval of git running also, with a large memory footprint,<br> > near 1GB. That seems rather excessive.<br> ><br> > At the same time, it dawned on me that my recent habit has been<br> > to run git pull, immediately followed by buildworld. Might it be<br> > prudent to wait (how long?) to let git finish any housekeeping<br> > triggered by the pull command? It seems likely that any overlap<br> > could readily lead to inconsistencies which might account for<br> > some of the buildworld problems I've been encountering lately.<br> <br> 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<br> <br> To find out of the src tree is pristine or dirty the build process uses git to find out.<br></blockquote><div><br></div><div>Though that's only for the kernel, not for world builds. Right?</div><div><br></div><div>Warner</div></div></div>home | help
Want to link to this message? Use this
URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CANCZdfrNw=AHLUcKxGzYoPQ7Zs=E2Wjp6Kqq4E3aU_LyBh_snA>