Date: Tue, 23 Apr 2024 11:12:41 -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: <DDA741CF-8681-4A96-8522-8AE19B62401B@yahoo.com> In-Reply-To: <B8EECFB4-70F0-49EC-92EE-7A1251156E7C@freebsd.org> References: <03736C90-EE54-47B3-AEA7-ED1AC0343B4B.ref@yahoo.com> <03736C90-EE54-47B3-AEA7-ED1AC0343B4B@yahoo.com> <B8EECFB4-70F0-49EC-92EE-7A1251156E7C@freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Apr 19, 2024, at 07:16, Philip Paeps <philip@freebsd.org> wrote: > On 2024-04-18 23:02:30 (+0800), Mark Millard wrote: >=20 >> 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 >> pd5512ae7b8c6_s75464941dc 34472 12282 (+9196) 107 (+77) 4753 = (+2247) 1390 (+529) 15940 parallel_build: Fri, 22 Mar 2024 11:05:01 GMT = 651:21:56 >>=20 >> p43e3af5f5763_sf5f08e41aa 19809 5919 (+3126) 137 (+100) 5363 = (+2741) 1395 (+522) 6995 parallel_build: Wed, 28 Feb 2024 15:46:14 GMT = 359:42:14 ampere2 >>=20 >> ampere2 alternates between trying to build main-arm64 and main-armv7, = so main-armv7 being stuck blocks main-arm64 from building. >>=20 >> One can see that all 13 job ID's show over 570 hours: >>=20 >> = http://ampere2.nyi.freebsd.org/build.html?mastername=3Dmain-armv7-default&= build=3Dpd5512ae7b8c6_s75464941dc >>=20 >> It is not random which packages are building when this happens. = Compare: >>=20 >> = http://ampere2.nyi.freebsd.org/build.html?mastername=3Dmain-armv7-default&= build=3Dp43e3af5f5763_sf5f08e41aa >>=20 >> By contrast, the 19 Feb 2024 from-scratch (full) build worked: >>=20 >> = http://ampere2.nyi.freebsd.org/build.html?mastername=3Dmain-armv7-default&= build=3Dpe9c9c73181b5_sbd45bbe440 >>=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 > I'll kill the build on ampere2 again. Thanks for the nudge. >=20 > We don't really have good monitoring for this. Also: builds should = time out after 36 hours. The fact that this one does not is a bug in = itself. >=20 > Philip [hat: clusteradm] I'll note that I've never managed to replicate the problem for building for armv7 on aarch64. But my context never has the likes of: QUOTE Host OSVERSION: 1500006 Jail OSVERSION: 1500015 . . . !!! Jail is newer than host. (Jail: 1500015, Host: 1500006) !!! !!! This is not supported. !!! !!! Host kernel must be same or newer than jail. !!! !!! Expect build failures. !!! END QUOTE but always has the two OSVERSION's the same, such as: Host OSVERSION: 1500015 Jail OSVERSION: 1500015 or, recently, Host OSVERSION: 1500018 Jail OSVERSION: 1500018 My bulk runs do go through the sequence where the hangups have repeated for main-armv7 on ampere2. I wonder what would happen if "Host OSVERSION" was updated (modernized) to match the modern "Jail OSVERSION" that would be used? =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?DDA741CF-8681-4A96-8522-8AE19B62401B>