Date: Fri, 26 Apr 2024 20:21:54 -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: <D98BB20E-11A5-45AE-87D9-011243CDF23B@yahoo.com> In-Reply-To: <E5605898-6EB9-4A28-9485-C4F9FBE8F404@freebsd.org> References: <03736C90-EE54-47B3-AEA7-ED1AC0343B4B.ref@yahoo.com> <03736C90-EE54-47B3-AEA7-ED1AC0343B4B@yahoo.com> <E5605898-6EB9-4A28-9485-C4F9FBE8F404@freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Apr 26, 2024, at 18:55, Philip Paeps <philip@freebsd.org> wrote: > On 2024-04-18 23:02:30 (+0800), Mark Millard 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 >> 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 > It looks like ampere2 is going to end up in this state again: >=20 > = https://pkg-status.freebsd.org/ampere2/build.html?mastername=3Dmain-armv7-= default&build=3Dp1c7a816cd0ad_s1bd4f769ca >=20 > It's got a couple of things stuck in -depends already. I'll keep an = eye on it for the next hour or two. If no progress is made, I'll kill = this build and force an upgrade. The next build will start at 01:01 UTC = Sunday. So we won't have long to wait before it tries again. >=20 > ampere1 is chewing away at llvm, and doesn't look stuck. >=20 > ampere3 has been upgraded. Output from the likes of: # ps -axldww could be interesting. As might be output from: # pstat -k -k PIDs_OF_STUCK_PROCESSES (kernel stack backtraces). =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?D98BB20E-11A5-45AE-87D9-011243CDF23B>