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.
https://portsfallout.com/server is somewhat messy for the beefy* "IPv4
Proxy" examples with lines that list multiple build environments or
just a rather old build environment:
Some links involved, like https://pkg-status.freebsd.org/beefy2/ , no
longer lead to someplace specific to the machine name.
beefy2 was decommissioned.
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?
There a lot of lines where the "build environment" list overall does
not match what the modern "IPv4 Proxy" buttons/links displays (when it
does for the machine name).
Note: the plain IPv4 and IPv6 icons do not link anywhere currently,
just the "IPv4 Proxy" of the 3 does.
Cc:ing dbaio, since he maintains portsfallout. :)
Philip
