Date: Tue, 01 Mar 2022 12:52:05 +0800 From: Philip Paeps <philip@freebsd.org> To: Ronald Klop <ronald-lists@klop.ws> Cc: clusteradm@freebsd.org, Ports Management Team <portmgr@freebsd.org>, freebsd-arm@freebsd.org Subject: Re: aarch64 build cluster and linux64.ko Message-ID: <65B16CD2-7F7A-4D4C-818F-B8E14FD74808@freebsd.org> In-Reply-To: <180462427.61.1644913953734@mailrelay> References: <1365005114.369.1643120837534@localhost> <993C6A92-7412-4426-903C-A2214B8A8031@freebsd.org> <55D4000E-2691-442D-9E46-E1966750344A@freebsd.org> <787825862.6.1644527984584@mailrelay> <1666CD64-2A90-4BBC-9DEF-C9BCED4738FF@freebsd.org> <180462427.61.1644913953734@mailrelay>
next in thread | previous in thread | raw e-mail | index | archive | help
On 2022-02-15 16:32:33 (+0800), Ronald Klop wrote: > One more question. > Do you know why the arm64 package builds are not registered on = > https://pkg-status.freebsd.org/builds?type=3Dpackage anymore? > > Because the pkg-status page has a nice way to compare two builds and = > spot regression (or progression). > https://pkg-status.freebsd.org/builds/default:default:main-arm64:pbd241= 2a3b974_sac678b4aaf:ampere2 I think I fixed this one. I believe it got stuck on trying to parse the = status of that build that was interrupted by upgrading. I cleared the = logs for that build and something seems to have changed. :) 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?65B16CD2-7F7A-4D4C-818F-B8E14FD74808>