Date: Fri, 04 Feb 2022 19:05:44 +0800 From: Philip Paeps <philip@freebsd.org> To: Ronald Klop <ronald-lists@klop.ws> Cc: Ports Management Team <portmgr@freebsd.org>, freebsd-arm@freebsd.org, clusteradm@freebsd.org Subject: Re: aarch64 build cluster and linux64.ko Message-ID: <F7DEF3FC-AD19-4F84-9C3C-30EC84D643B3@freebsd.org> In-Reply-To: <1041004715.975.1643961552511@localhost> References: <1041004715.975.1643961552511@localhost>
next in thread | previous in thread | raw e-mail | index | archive | help
On 2022-02-04 15:59:12 (+0800), Ronald Klop wrote: > Philip Paeps wrote: >> On 2022-01-26 08:58:20 (+0800), Philip Paeps wrote: >> I've upgraded one of the package builders (ampere1.nyi.freebsd.org) >> with a build including linux64.ko. The module seems to load. >> portmgr might need to do something to the builds to actually use it >> though. >> >> I'll upgrade the other aarch64 package builder when it finishes its >> current build. > > Thank you. 122arm64 quarterly build fine. 130arm64 quarterly is > hanging in :sanity: for 48 hours already. I think it is stuck. Would > you have time to check? If I understand the automation/scheduling correctly, ampere1 started a new 130arm64 quarterly build while I was upgrading it. That build got stuck in :sanity:. After being upgraded, it started on the next build in the queue, which is still running now. I believe it should start on a 130arm64 build after this. Philip -- Philip Paeps Senior Reality Engineer Alternative Enterprises
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?F7DEF3FC-AD19-4F84-9C3C-30EC84D643B3>