Re: FYI: ampere2 based port-package builds were not restarted with beefy15/21/22 after the crash fix to the ports tree
Mark Millard <[email protected]>
| Newsgroups | gmane.os.freebsd.devel.ports |
|---|---|
| Message-ID | <[email protected]> |
On Jul 18, 2025, at 22:39, Philip Paeps <[email protected]> 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