From Newsgroup: muc.lists.freebsd.ports
On Jul 18, 2025, at 22:39, Philip Paeps <
philip@freebsd.org> wrote:
On 2025-07-19 00:35:27 (+0800), Mark Millard wrote:
There was a problem with the ports tree that lead to ampere2, beefy15,
beefy21, and beefy22 failing to even queue any packages.
After the ports tree was fixed to not cause that, beefy15, beefy21,
and beefy22 were restarted using a vintage of the tree that had the
fix. That was some 28+ hours ago.
But ampere2 has not been restarted yet.
I don't start builds. I don't scale.
pkgmgr is in charge of the builds.
Yea, I recently saw that the system had been started
somewhat over 4 hrs ago, with the next block of other
systems that had builds started a little before that.
So ampere2 was apparently not having its own problems
as well but just needed to have builds started normally.
I should not infer more than ampere1 having
stops-operating problems. (I think it has been the only
one panicking on a fairly regular basis.)
Sorry for the noise.
===
Mark Millard
marklmi at yahoo.com
--
Posted automagically by a mail2news gateway at muc.de e.V.
Please direct questions, flames, donations, etc. to
news-admin@muc.de
--- Synchronet 3.21a-Linux NewsLink 1.2