Skip to content

Conversation

@GeorgeSapkin
Copy link
Member

Switch simple jobs to use a single CPU runner based on ubuntu-slim.

I tried to pick simple-looking jobs without any build or docker-related steps.

I've only tested building packages in the main feed.

Link: https://docs.github.com/en/actions/reference/runners/github-hosted-runners#single-cpu-runners

Switch simple jobs to use a single CPU runner based on ubuntu-slim.

Link: https://docs.github.com/en/actions/reference/runners/github-hosted-runners#single-cpu-runners
Signed-off-by: George Sapkin <[email protected]>
@BKPepe
Copy link
Member

BKPepe commented Nov 10, 2025

I think somewhere, there is missing one important detail that switching to single CPU runner creates a condition that the job must be completed within 15 minutes.

@GeorgeSapkin
Copy link
Member Author

I only changed trivial setup, preparation, checking, etc. jobs, i.e. non-build ones, that I think should fail if they are taking longer than 15 minutes. Does anything specific look concerning?

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.

2 participants