Hi, pkg building for arm64.aarch64 appears to be broken on ampere2 since mid-March. It looks like armv7 pkg building, which appears stuck in a loop, is holding it up. https://lists.freebsd.org/archives/freebsd-ports/2024-April/005975.html
Thanks for letting us know. This has been happening to the builds on ampere2 a couple of times. Antoine: can you see anything wrong here? I can kill the build and/or reboot the machine, unless you want to investigate?
I already rebooted it. It seems that armv7 is not in a good shape..
Wouldn't it be best if main-arm64 had its own builder? Just a suggestion. Because what's happening now appears to be that building for tier-2 arch ports stops builds for a tier-1 arch from happening, which is suboptimal.
That would make sense. But we don't have enough aarch64 hardware online for a dedicated builder. We have a beefy 2U aarch64 machine sitting in storage in New Jersey. That needs to be shipped to Chicago to be brought online. This is blocked on the FreeBSD Foundation.
It has been suggested on the mailing list that perhaps running a newer -CURRENT in the build jail than the -CURRENT running on the underlying hardware may be the problem. ampere2 has just started a quarterly for armv7. I'll keep an eye on the build. If it looks like it's looping, I will kill it and force the upgrade.
Hi, The problem is happening again, with https://pkg-status.freebsd.org/ampere2/build.html?mastername=main-armv7-default&build=pd65a728b53a9_scadd2ca217 stuck at 14:00:16 runtime. I dunno if it's looping - it's just stuck/wedged with the stopped runtime
It looks like the machine is doing something: http://ampere2.nyi.freebsd.org/build.html?mastername=main-arm64-default&build=p2ce6ce9f7525_se461c7bc7dd Not sure why the other build looks stuck. poudriere status shows it's working on this: - default main-arm64 p2ce6ce9f7525_se461c7bc7dd parallel_build 34910 48 0 478 975 0 33409 00:18:38 https://pkg-status.freebsd.org/ampere2/build.html?mastername=main-arm64-default&build=p2ce6ce9f7525_se461c7bc7dd For what it's worth, the machine is running the 24 April build -- same as the other builders.