Date: Mon, 29 Apr 2024 19:54:09 -0700 From: Mark Millard <marklmi@yahoo.com> To: Philip Paeps <philip@freebsd.org> Cc: void <void@f-m.fm>, FreeBSD Mailing List <freebsd-ports@freebsd.org>, Current FreeBSD <freebsd-current@freebsd.org> Subject: Re: pkg server for current/arm64 stopped ? [main-armv7 on ampere2, elapsed so far: 651:21:56] Message-ID: <046DE453-9F01-4D07-9E14-EF22E537A163@yahoo.com> In-Reply-To: <E97F1D20-55BF-4D6A-AC02-07FFD264931C@freebsd.org> References: <03736C90-EE54-47B3-AEA7-ED1AC0343B4B@yahoo.com> <A5A0731B-6BA7-45BE-B8CF-2165852FA3B0@yahoo.com> <E97F1D20-55BF-4D6A-AC02-07FFD264931C@freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Apr 28, 2024, at 18:06, Philip Paeps <philip@freebsd.org> wrote: > On 2024-04-18 23:14:22 (+0800), Mark Millard wrote: >> On Apr 18, 2024, at 08:02, Mark Millard <marklmi@yahoo.com> wrote: >>> void <void_at_f-m.fm> wrote on >>> Date: Thu, 18 Apr 2024 14:08:36 UTC : >>>=20 >>>> Not sure where to post this.. >>>>=20 >>>> The last bulk build for arm64 appears to have happened around >>>> mid-March on ampere2. Is it broken? >>>=20 >>> main-armv7 building is broken and the last completed build >>> was the one started on Mon, 19 Feb 2024 12:32:10 GMT. It >>> gets stuck making no progress until manually forced to stop, >>> which leads to huge elapsed times for the incomplete builds: >>>=20 >>> [...] >>>=20 >>> My guess is that FreeBSD has something that broken after bd45bbe440 >>> that was broken as of f5f08e41aa and was still broken at 75464941dc = . >>>=20 >>=20 >> One thing of possible note: >>=20 >> Failing . . . >>=20 >> Host OSVERSION: 1500006 >> Jail OSVERSION: 1500014 >=20 > I have finished a package builder refresh this morning. All our = builder hosts (except PowerPC - I don't touch those) are now on = main-n269671-feabaf8d5389 (OSVERSION 1500018). >=20 > ampere1 successfully finished its 140releng-armv7-quarterly build, so = it looks like the problem with stuck builds was limited to ampere2 = building main-armv7. I'll keep a close eye on this one when it starts = its next build. >=20 I see that main-armv7 started. It queued only 31935 instead of the prior 34528 (or more): it is doing = an incremental build instead of a full build. For example, pkg was not = built but instead the prior build is in use. Thus bad results from the prior build might be involved in this new build. I'd recommend forcing a full "poudriere bulk -c -a" that does a = from-scratch build for the purposes of the main-armv7 test. =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?046DE453-9F01-4D07-9E14-EF22E537A163>