Skip to content

Conversation

@ldionne
Copy link
Member

@ldionne ldionne commented May 27, 2025

The libc++ self-hosted runner infrastructure has been unstable for a while. Instead, switch over to the runners used for the rest of LLVM's premerge testing, which are better supported.

This also allows us to remove the "job restarter" workflow, which isn't needed anymore since the LLVM-wide runners can't get preempted at arbitrary times.

NOTE: This PR is exploratory only. While we do have an ideal goal to move the libc++ runners to the common monorepo infrastructure, there are other questions to answer before we can do that. The goal of this PR is mainly to shake out any obvious technical issue in making that move.

The libc++ self-hosted runner infrastructure has been unstable for
a while. Instead, switch over to the runners used for the rest of
LLVM's premerge testing, which are better supported.

This also allows us to remove the "job restarter" workflow, which
isn't needed anymore since the LLVM-wide runners can't get preempted
at arbitrary times.

NOTE: This PR is exploratory only. While we do have an ideal goal to
      move the libc++ runners to the common monorepo infrastructure,
      there are other questions to answer before we can do that. The
      goal of this PR is mainly to shake out any obvious technical
      issue in making that move.
@ldionne
Copy link
Member Author

ldionne commented Sep 4, 2025

Closing since this has now been done by @cmtice and @boomanaiden154 .

@ldionne ldionne closed this Sep 4, 2025
@ldionne ldionne deleted the review/switch-to-llvm-premerge-runners branch September 4, 2025 14:46
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant