aarch64 pkg build seems broken/hanging

[Philip Paeps]

On 2020-12-22 19:42:07 (+0800), Ronald Klop wrote:
> On Mon, 30 Nov 2020 23:20:26 +0100, Philip Paeps <philip at freebsd.org> 
> wrote:
>> On 2020-11-30 23:41:02 (+0800), Ronald Klop wrote:
>>> Philip Paeps wrote:
>>>> The new aarch64 systems arrived at the data centre on Friday (local 
>>>> time) and were installed and configured in the cluster yesterday 
>>>> (my time).  They'll start running builds soon.  Packages will start 
>>>> appearing on the mirrors shortly after.
>>>
>>> Great news! Thanks for the update.
>>> Do you have some nice details about the new systems? Just for my 
>>> curiosity. Probably a bit better than the RPI4 I installed to build 
>>> my packages in the meantime. :-)
>>
>> The new systems are Ampere eMAG based: 32 cores, 128G memory.  
>> They're currently set up with two spinning rust drives.  We'll 
>> probably replace those with four SSDs for better IO.
>>
>> Full specs here:
>> https://amperecomputing.com/wp-content/uploads/2019/04/Lenovo_ThinkSystem_HR330A_PB_20190409.pdf
>
> I see packages flowing for 12 and 13 again. Thank you very much.

I'm glad to hear they're being used! :-)

> Will the new poudriere get published in 
> https://pkg-status.freebsd.org/builds?type=package also?

I'll try to figure out how that works and/or poke someone about it.

> Or is the server reachable via some URL?
> I would love to see the build logs of some failed ports.

You can find the build logs on http://ampere1.nyi.freebsd.org and 
http://ampere2.nyi.freebsd.org.  I'll see what I can do about hooking 
those up to the pkg-status voodoo.  Thanks for pointing that out.

Philip

-- 
Philip Paeps
Senior Reality Engineer
Alternative Enterprises