FreeBSD libc++ CI needs upgrading

[philnik777]

The libc++ FreeBSD runner is still on Clang 17, which we don't support anymore officially. @DimitryAndric could you (or whoever is responsible for the runner) update it soon?

[DimitryAndric]

@emaste is more closely associated with this runner.

[emaste]

Yep I'll get it updated soon

[llvmbot]

@llvm/issue-subscribers-infrastructure

Author: Nikolas Klauser (philnik777)

The libc++ FreeBSD runner is still on Clang 17, which we don't support anymore officially. @DimitryAndric could you (or whoever is responsible for the runner) update it soon?

[ldionne]

@emaste The FreeBSD CI node seems to be stuck since last Friday, can you please take a look? e.g. https://buildkite.com/organizations/llvm-project/unclustered/agents/019378de-e333-4648-8c5f-1434c55411a4

[ldionne]

@emaste Ping, this has been going on for over 10 days.

[ldionne]

@emaste Ping.

[ldionne]

@emaste @DimitryAndric Any news?

[ldionne]

@emaste @DimitryAndric Hi folks, this is going to be my last ping on this thread. The FreeBSD CI has been broken for 2.5 months now. According to our support policy, we only support platforms for which we have CI. If there is no progress on this issue (or at least an ack.), I will proceed to remove the documentation of FreeBSD support in 7 days since we are currently running without CI. Some folks have been asking questions about eg the status of time zone support in FreeBSD, and we can't guarantee it works without CI, but we also can't make a statement about it being unsupported. This is the kind of situation we want to avoid.

[emaste]

The host OS was updated at the end of November along with installing Clang 19. I tried to find folks on libcxx in Discord to help check the buildkite status but didn't get a reply. Sorry I missed the followups in this thread -- @DimitryAndric pinged me on IRC just now.

The link above gives me a 404.

Buildkite is running on the host but I'm not sure how to check status (from either end).

[ldionne]

Ack, thanks. I must have missed your pings on Discord. Let's see if #127687 works.