Re: FYI: https://pkg-status.freebsd.org/?all=1&type=package does not cover beefy20 , beefy21 , or beefy22 yet

From: Mark Millard <marklmi_at_yahoo.com>
Date: Wed, 29 May 2024 04:40:33 UTC
On May 28, 2024, at 21:13, Philip Paeps <philip@freebsd.org> wrote:
> 
> On 2024-05-29 12:03:52 (+0800), Mark Millard wrote:
>> On May 28, 2024, at 20:45, Philip Paeps <philip@freebsd.org> wrote:
>>> On 2024-05-29 11:37:04 (+0800), Mark Millard wrote:
>>>> In the mean time: The "IPv4 Proxy" buttons/links on the lines for beefy2[012] at https://portsfallout.com/server allow looking at the build activity on those machines. The lines also show which build environment (such as "140amd64-default" or "140amd64-quarterly"). The "IPv4 Proxy" buttons/links in question translate to:
>>>> 
>>>> https://pkg-status.freebsd.org/beefy20/
>>>> https://pkg-status.freebsd.org/beefy21/
>>>> https://pkg-status.freebsd.org/beefy22/
>>>> 
>>>> After that click the Build link on the page that is shown.
>>> 
>>> The package builders live in an IPv6-only VLAN.  The reverse proxy on https://pkg-status.freebsd.org is for the convenience of users who are only connected to the legacy 20th century IPv4 internet.
>>> 
>>> If you are on the 21st century internet, you can get directly to e.g. http://beefy18.nyi.freebsd.org.
>> 
>> http://beefy18.nyi.freebsd.org/ works for me.
>> 
>> http://beefy21.nyi.freebsd.org/ "Can't Fine the Server" for me.
>> but . . .
>> https://pkg-status.freebsd.org/beefy21/ works for me.
> 
> Try beefy21.chi.freebsd.org -- the new beefyX are in Chicago.

That works in my context. Thanks.

> (There was a firewall rule in the way.  This was removed.)
> 
>>>> Some links, like https://pkg-status.freebsd.org/beefy11/ , lead to the old place for a type of build, not to the modern place that is on a newer machine.
>>> 
>>> As far as I can tell, beefy11 and beefy18 show similar pages.  I can't tell which is "older" and "newer".  Am I misunderstanding something?
>> 
>> https://pkg-status.freebsd.org/beefy11/ shows "140i386-default 804916ac9382" (Master and Build).
>> https://pkg-status.freebsd.org/beefy18/ shows "main-amd64-default pb6f9255af153_sdeab57178f0"
>> 
>> I think you meant 21 instead of 18:
>> 
>> https://pkg-status.freebsd.org/beefy21/ shows "140i386-default b6f9255af153".
>> 
>> "140i386-default 804916ac9382" is older (last build done on beefy18, most likely).
>> "140i386-default b6f9255af153" is newer (most recent build in-progress/done on beefy21).
> 
> I must be blind.  I can't tell the difference?

804916ac9382 is an older (partial) commit hash, using the Build link and looking around . . .
tinyca-0.7.6_2: build started at Mon May 20 01:28:44 UTC 2024
also shows only jobs slots 01 .. 10

b6f9255af153 is a  newer (partial) commit hash, using the Build link and looking around . . .
tinyca-0.7.6_2: build started at Tue May 28 16:21:12 UTC 2024
also shows      jobs slots 01 .. 42

"140i386-default" is the same for both but the rest is not: different poudriere bulk runs are referenced.

> I shall insert more coffee into my body and look again this afternoon. :)

===
Mark Millard
marklmi at yahoo.com