[Note: The new main-amd64 (beefy18) example reported is still building but has taken over 72 hrs longer than any other prior example. There is a major performance change involved compared to builds started before April. Slower hardware makes that more obvious than the fastest hardware does.]
On Apr 4, 2025, at 20:25, Mark Millard <mark...@yahoo.com> wrote: > On Apr 4, 2025, at 09:04, Mark Millard <mark...@yahoo.com> wrote: > > >> Longest ever prior bulk build of main-arm64-default (HHH:MM:SS): 171:50:51 >> (Host OSVERSION: 1500019) >> >> On going bulk build: Built 11348 Remaining 23676 (HHH:MM:SS): 85:57:28 >> >> This suggests possibly more like 230+ Hrs for the completed build. >> >> >> Now (0n going bulk build, first such): >> >> Host OSVERSION: 1500035 >> Jail OSVERSION: 1500035 >> >> Previously (recent): >> >> Host OSVERSION: 1500028 >> Jail OSVERSION: 1500034 >> >> (or before). Longest build time: 163:20:35 >> That timing is for: >> >> https://pkg-status.freebsd.org/ampere2/build.html?mastername=main-arm64-default&build=p02dd5021d6f9_s717adecbbb5 >> >> >> It might be appropriate to monitor: >> >> https://pkg-status.freebsd.org/ampere2/build.html?mastername=main-arm64-default&build=p25bf3a3260c7_s680d34896c3 >> >> >> Note: https://pkg-status.freebsd.org/builds?type=package&all=1 can be >> sorted to find the 171:50:51 that I list. > > I forgot to mention using searching by main-arm64 . > >> I''ll note that it was >> for: >> >> Host OSVERSION: 1500019 >> Jail OSVERSION: 1500023 >> > > Sorting the list shown by (searching for beefy22): > > https://pkg-status.freebsd.org/builds?type=package&all=1 > > by decreasing elapsed time shows that 142amd64-default has > the top time by over 9 extra hours, despite building fewer > packages: > > 58:51:19 for 142amd64-default 25bf3a3260c7 to reach the Remaining==0 crashed: > Status, building 34744 packages > 49:37:29 for 141amd64-default 182ff2d0ad1b to reach the Remaining==0 done: > Status, building 36022 packages > > Note: > For 58:51:19, the last job has "ended at Apr 3 11:48:00 UTC 2025" > and the Started (UTC) column has "01 Apr 2025 01:02:20 GMT". So the > "crashed:" part does not seem to have contributed much to the > overall time. > It happens for 142i386-default (beefy21) as well, this time taking somewhat over 10 hrs more for a more similar number of packages: 50:40:16 for 142i386-default 25bf3a3260c7 to reach the Remaining==0 done: Status, building 34415 packages 40:22:44 for 141i386-default 35e33b5b9186 to reach the Remaining==0 done: Status, building 34578 packages It happens for main-amd64-default (beefy18) as well, so far taking 72 hrs+ longer but not yet having finished building packages: 168:11:10 for main-amd64-default pad39cc941617_s7a490725045, building 26636 packages so far, 9338 Remaining 96:28:10 for main-amd64-default p9229caa5b2ac_s780a4667bbd, building 35771 packages, 0 Remaining === Mark Millard marklmi at yahoo.com
