On Fri, Apr 4, 2025 at 10:25 PM Mark Millard <[email protected]> wrote:
> Kevin Oberman <rkoberman_at_gmail.com> wrote on > Date: Sat, 05 Apr 2025 04:34:21 UTC : > > > On Fri, Apr 4, 2025 at 8:11 PM Philip Paeps <[email protected]> wrote: > > > > > On 2025-04-05 00:37:47 (+0800), Kevin Oberman wrote: > > > > There appear to have been no successful package updates for FreeBSD > > > > since > > > > EOL for 14.1-AMD64. The only build for 142amd64-default that one > > > > appears to > > > > have crashed. As a result, I am seeing a growing list of packages > that > > > > are > > > > not getting updated. The last successful build was the final build on > > > > 14.1 > > > > last Monday March 30. > > > > > > > > Any idea how long it might be or how serious the issue is? It looks > > > > like > > > > all package builds were completed, though there does appear to have > > > > been a > > > > significant jump in failed builds since the previous build (14.1 > > > > default) > > > > > > We upgraded the package builders to recent -CURRENT last week and the > > > release/X build jails are no longer working. If we have to reinstall > > > the builders with older -CURRENT, it's at least a week of work. If > > > someone can fix the actual bug in -CURRENT, it'll take us about an > > > hour-ish to upgrade all the builders. > > > > > > I don't know what the bug is. But it's easy enough to reproduce: run > > > poudriere in a release/X jail on -CURRENT and watch it explode. > > > > > > If it's any help, hte final 14.1 build was very strange. While the build > > completed after about 23 hours, during the build there were always a > large > > number of builds in prep parts before starting the actual builds. I see > the > > same issue in the build that just started on beefy21, though that build > has > > just started 3.5 hours ago. I just never recall seeing so many > lib-depends > > and build-depends. It's like the builds are queued differently. > > It is pkg 2.1.0 doing extra activity that is rather time expensive. > pkg 1.21.3 does not do this extra activity. > > > Likely > > nothing, but it looks very odd. > > Definitely something. The official bulk builds on beefy17 > and beefy18 now take over twice as long overall as they > did when pkg 1.21.3 was in use. Looks like ampere2 will > be similar. > > It is not as extreme on the fastest hardware, such as > beefy21 and beefy22. But there still is notably more > time for those as well. > > > === > Mark Millard > marklmi at yahoo.com Pretty significant on 21 and 22, as well once you get used to most builds (<10,000 packages) completing in 18-24 hours and big builds (build all packages) tooks around 48 hours. The full build of 14.2 took almost 59 hours and skipped over 1300 or a bit less than 1000 more than were skipped on 14.1 builds before the last one. -- Kevin Oberman, Part time kid herder and retired Network Engineer E-mail: [email protected] PGP Fingerprint: D03FB98AFA78E3B78C1694B318AB39EF1B055683
