Date: Sun, 28 Jan 2024 17:13:24 -0800 From: Mark Millard <marklmi@yahoo.com> To: david@catwhisker.org, FreeBSD-STABLE Mailing List <freebsd-stable@freebsd.org> Subject: Re: Should changes in src/usr.sbin/bhyve/ trigger an llvm rebuild? Message-ID: <A20E1EB3-1D51-44FF-840F-69DB41C5CEA7@yahoo.com> In-Reply-To: <Zbbrr6fh3sQ_VX-8@albert.catwhisker.org> References: <EAD76C2C-065E-4EFA-901F-1C0FD13FFC65.ref@yahoo.com> <EAD76C2C-065E-4EFA-901F-1C0FD13FFC65@yahoo.com> <ZbZ2u9FlUhvb1orU@albert.catwhisker.org> <5BCB8F1A-B5D5-4506-87E1-8B26E713C6F5@yahoo.com> <ZbbPyYNtF6prkdtd@albert.catwhisker.org> <B1231700-D7A1-4190-AA2A-495CEA954535@yahoo.com> <8A79DE24-403E-4E73-82B6-0E5CF4F27604@yahoo.com> <Zbbrr6fh3sQ_VX-8@albert.catwhisker.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Jan 28, 2024, at 16:05, David Wolfskill <david@catwhisker.org> wrote: > On Sun, Jan 28, 2024 at 03:00:59PM -0800, Mark Millard wrote: >> ... >> To be clear, referencing details of your context: >>=20 >> When you had the stable/14 machines at 1c090bf880bf: >>=20 >> A) You built (META_MODE): 63a7e799b32c >> B) You installed: 63a7e799b32c >> C) You rebooted into: 63a7e799b32c >>=20 >> I'm claiming that next doing: >>=20 >> D) build again (still META_MODE): 63a7e799b32c >>=20 >> would have rebuilt llvm at that point, the >> time-relationship cause(s) being set up >> during (B). >=20 > As it happens, I rather fumble-fingered the (intended) reboot on the = 2nd > laptop (and started another rebuild instead). >=20 > And I do these within script(1), as it's handy to have a record. >=20 > Note that this differes from the sequence you cite above, in that I > failed to do the reboot. >=20 > So I powered it back up and -- without updating sources (or the local > repo mirror, for that matter) -- did another rebuild. >=20 I'm having trouble identifying the detailed sequencing being reported below. Doing on one machine: installworld buidlworld buildworld buildworld . . . Will only take large times for the first one (potentially). But doing: installworld buidlworld installworld buildworld installworld buildworld . . . Can have each buildworld take large times depending the the details involved. I need to understand more about what happened before each buildworld on each machine to know what sort of timestamp relationships are involved for files. installworld can significantly change various timestamp relationships. > Here is an extract of some salient lines from the typescript file: >=20 > g1-48(14.0-S)[4] egrep ' built in |Installing .* = (started|completed)|Removing old libraries| stable/14-n' s1 > FreeBSD g1-48.catwhisker.org 14.0-STABLE FreeBSD 14.0-STABLE #38 = stable/14-n266551-63a7e799b32c: Sat Jan 27 11:40:05 UTC 2024 = root@g1-48.catwhisker.org:/common/S1/obj/usr/src/amd64.amd64/sys/CANARY = amd64 1400506 1400506 >>>> World built in 2351 seconds, ncpu: 8, make -j16 Was a prior step (ignoring reboots, say) an installworld of 63a7e799b32c, with no other buidlworlds after the installworld? (I'm wording for major steps or my description the possibilities would get rather complicated and large.) >>>> Kernel(s) CANARY built in 898 seconds, ncpu: 8, make -j16 >>>> Installing kernel CANARY completed on Sun Jan 28 12:25:27 UTC 2024 >>>> Installing everything started on Sun Jan 28 12:25:57 UTC 2024 >>>> Installing everything completed on Sun Jan 28 12:28:01 UTC 2024 > FreeBSD g1-48.catwhisker.org 14.0-STABLE FreeBSD 14.0-STABLE #38 = stable/14-n266551-63a7e799b32c: Sat Jan 27 11:40:05 UTC 2024 = root@g1-48.catwhisker.org:/common/S1/obj/usr/src/amd64.amd64/sys/CANARY = amd64 1400506 1400506 >>>> World built in 116 seconds, ncpu: 8, make -j16 Was a prior step (ignoring reboots, say) an installworld of 63a7e799b32c, with no other buidlworlds after the installworld? Is the answer different here? >>>> Kernel(s) CANARY built in 920 seconds, ncpu: 8, make -j16 >>>> Installing kernel CANARY completed on Sun Jan 28 12:47:55 UTC 2024 >>>> Installing everything started on Sun Jan 28 12:48:25 UTC 2024 >>>> Installing everything completed on Sun Jan 28 12:50:01 UTC 2024 > FreeBSD g1-48.catwhisker.org 14.0-STABLE FreeBSD 14.0-STABLE #40 = stable/14-n266554-2ee407b6068a: Sun Jan 28 12:39:17 UTC 2024 = root@g1-48.catwhisker.org:/common/S1/obj/usr/src/amd64.amd64/sys/CANARY = amd64 1400506 1400506 >>>> Removing old libraries > FreeBSD g1-48.catwhisker.org 14.0-STABLE FreeBSD 14.0-STABLE #40 = stable/14-n266554-2ee407b6068a: Sun Jan 28 12:39:17 UTC 2024 = root@g1-48.catwhisker.org:/common/S1/obj/usr/src/amd64.amd64/sys/CANARY = amd64 1400506 1400506 >>>> World built in 124 seconds, ncpu: 8, make -j16 Was a prior step (ignoring reboots, say) an installworld of 63a7e799b32c with no other buidlworlds after the, installworld? >>>> Kernel(s) CANARY built in 901 seconds, ncpu: 8, make -j16 >>>> Installing kernel CANARY completed on Sun Jan 28 23:34:39 UTC 2024 >>>> Installing everything started on Sun Jan 28 23:35:09 UTC 2024 >>>> Installing everything completed on Sun Jan 28 23:37:16 UTC 2024 > FreeBSD g1-48.catwhisker.org 14.0-STABLE FreeBSD 14.0-STABLE #41 = stable/14-n266554-2ee407b6068a: Sun Jan 28 23:26:10 UTC 2024 = root@g1-48.catwhisker.org:/common/S1/obj/usr/src/amd64.amd64/sys/CANARY = amd64 1400506 1400506 >>>> Removing old libraries > g1-48(14.0-S)[5] >=20 > (The ">>> Removing old libraries" is an artifact from "make > delete-old-libs", which I do on the first reboot after a build.) >=20 > If we just look at the "make buildworld" times, we see: >=20 >>>> World built in 2351 seconds, ncpu: 8, make -j16 >>>> World built in 116 seconds, ncpu: 8, make -j16 >>>> World built in 124 seconds, ncpu: 8, make -j16 >=20 > I suggest that -- within *this* "experiment's" error -- 116 sec is not > significantly different from 124 sec, but that 2351 sec is = significantly > different from either. >=20 > .... =3D=3D=3D Mark Millard marklmi at yahoo.com
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?A20E1EB3-1D51-44FF-840F-69DB41C5CEA7>