Re: A better alternative to having builds of main-armv7-default fully disabled and last-built be months out of date

From: Philip Paeps <philip_at_freebsd.org>
Date: Mon, 15 Jul 2024 00:20:55 UTC 
Sorry for not following up to this thread earlier.
I've been occupied elsewhere in the cluster.

On 2024-07-07 16:25:32 (+0800), Mark Millard wrote:
> On Jul 6, 2024, at 21:35, Michal Meloun <meloun.michal@gmail.com> 
> wrote:
>> On 07.07.2024 5:42, Mark Millard wrote:
>>> main's armv7 packages that are distributed are getting to be months
>>> behind because of the build hangups preventing the builds on 
>>> ampere2.

It's worth reinforcing that this only affects main (15-CURRENT).  Our 
stable/13 and stable/14 packages for armv7 are reasonably up to date.  
Reasonably for a tier-2 architecture anyway.  Whatever is causing this, 
it's only in main.

> The only known failures are on ampere2 as far as I know.
> As far as I know there is no known way to configure to
> match the formal build procedures used on ampere2.

According to the current schedule, armv7 builds happen on ampere3, not 
ampere2:

ampere1: - quarterly arm64.aarch64 13.3-RELEASE 133arm64 -a
ampere1: - quarterly arm.armv7 releng/13.3 133releng-armv7 -a
ampere1: - quarterly arm64.aarch64 14.0-RELEASE 140arm64 -a
ampere1: - quarterly arm.armv7 releng/14.0 140releng-armv7 -a
ampere2: - default arm64.aarch64 main main-arm64 -a
ampere3: - default arm64.aarch64 13.3-RELEASE 133arm64 -a
ampere3: - default arm.armv7 releng/13.3 133releng-armv7 -a
ampere3: - default arm64.aarch64 14.0-RELEASE 140arm64 -a
ampere3: - default arm.armv7 releng/14.0 140releng-armv7 -a

I've attached the poudriere.conf from that machine.  It's the same one 
we have on all the builders.

>> I've seen some strange live lockups in arm32 jail, but never managed 
>> to reproduce it.
>
> On what kind(s) of hardware?
> Any kind of relevant context known?

In case it helps: ref15-aarch64.freebsd.org (available to all 
developers) is an identical configuration as ampereX.nyi.freebsd.org.  
The former has a newer BIOS (for some reason) but that hopefully should 
not make a difference.  If we reach the point where we think the BIOS 
version matters, I can try to upgrade the BIOS on the ampereXen.

smbios.bios.reldate="06/25/2020"
smbios.bios.revision="1.14"
smbios.bios.vendor="LENOVO"
smbios.bios.version="hve104q-1.14"

smbios.bios.reldate="05/30/2019"
smbios.bios.revision="1.8"
smbios.bios.vendor="LENOVO"
smbios.bios.version="HVE104J-1.08"

Philip